As we've seen (see what you missed), Node.js is all the rage these days. Great model, but you better like JavaScript and the V8. Ever wondered what Node would look like on the JVM? Just ask Matt Stine to tell you about Vert.x!
Vert.x is a new framework for writing easily scalable applications. It is the marriage of the event-driven, non-blocking I/O programming model popularized by Node.js with the proven performance and concurrency found on the JVM.
Vert.x is polyglot, currently allowing you to write your programs in JavaScript, Ruby, Groovy or Java (with support forthcoming for Scala, Clojure and Python). It provides a very easy concurrency model, allowing you to write single-threaded code that is always executed by the same exact thread. It provides parallelism by scaling seamlessly across all available cores. With all of this is provided much the same programming model you may be used to in the Node.js world, with the added capability of a distributed event bus which spans client and server side, shared immutable data, and background workers.
This session will provide an introduction to Vert.x, with live demos of its feature and the construction of a real case-study application.
As always, the venue, food, drinks, and giveaways will be provided by our sponsors. Special thanks goes out to Jill Rupp from APEX Systems for arranging for Matt to speak at our group!
About Matt Stine:
Matt Stine is an Enterprise Java/Cloud consultant based in Memphis, TN. He is a twelve year veteran of the enterprise software and web development industries, with experience spanning the healthcare, biomedical research, e-commerce, and retail store domains.
Matt has spoken at conferences ranging from JavaOne to CodeMash and has published several articles for Agile Zone, GroovyMag and NFJS the Magazine, as well as the Selenium 2.0 DZone Refcard. Matt is also the founder of the Memphis/Mid-South Java User Group.
His current areas of interest include lean/agile software development, software architecture, mobile application development and functional languages.
Comments