TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Understanding Vert.x Architecture - Part II | CUBRID Blog

1 pointsby kadishmalalmost 12 years ago

1 comment

eipalmost 12 years ago
"I don't know much about Spring, but In Vert.x 1.x each Verticle that is deployed has its own classloader, so it's hard to share a context across verticles." -- Tim Fox (Vertx creator)<p>"A vert.x instance guarantees that a particular verticle instance is always executed by the exact same thread. This gives you a huge advantage as a developer, since you can program all your code as single threaded. Well, that won't be a big deal to you if you are coming from JavaScript where everything is single threaded, but if you're used to multi-threaded programming in Java, Scala, or even Ruby, this may come as a huge relief" -- lol<p><a href="http://www.youtube.com/watch?v=bzkRVzciAZg" rel="nofollow">http://www.youtube.com/watch?v=bzkRVzciAZg</a>