This is a totally new thing for me. I want to keep my ear to the ground with Vert.x, and what better way to force myself to be disciplined about it than to commit to a weekly blog entry? Let’s see if I can keep up with it.
What the Vert.x developer community was up to this week:
Tim Fox started a discussion about release planning for Vert.x 3.0. Having been a casual observer over the past few months, I know they’ve been doing some innovative stuff that even I’m having trouble following. Getting it all locked down and packaged into a final release is going to force the community to crystallize it all. As it stands right now, they’re looking for a 3.0 beta at the end of January and a final release at the end of March.
Rajith started an effort to integrate AMQP into Vert.x so that Vert.x looks like any other AQMP message service. I understand this to be an event bus-type integration that Vert.x could play alongside any other message queuing technology that supports AMQP. Early in the week, Rajith was proposing something at the core level, but it looks like the community settled on keeping it a “citizen of ext.” Having Vert.x verticles sitting alongside a bunch of message queues seems to make some kind of natural sense, but I need to think about it more to fully grasp its implications.
Tim Fox introduced a CORS feature as well as a new verx-auth module, which currently uses LDAP (based on Apache Shiro for now). He’s looking to add database-/JDBC-based authentication/authorization later.
The community continued to discuss how they can make the modules marketplace a little more vibrant. While I suppose there’s a lot of ways of dealing with this, I think they’re being smart to focus on the current Maven repos. The community is trying to figure out how to automatically discover new modules out there in the repository universe that really belong in the modules catalog.
Oh, and the #vertx channel on IRC is now logged, so you can be just as voyeuristic as me.
New Vert.x job listings for the week:
There’s a senior software engineer posting in the Annapolis area that seems to require Vert.x experience and security clearance — interesting!