This data is specific to March 2017. If you want the latest data in the Java Web Frameworks index, be sure to check out and bookmark the main Java Web Frameworks Index homepage.
This is our second blog post about the Web Frameworks Index! Our first, which we posted last month gave an overview of what the program was all about. Over the coming months, we’ll be providing updated data points about how each Java web framework is performing in our index.
In this whitepaper, we describe the performance pipeline, a concept of mapping performance related work and activities towards the stages of a software delivery pipeline. The main idea behind the performance pipeline is to make sure that the development team is aware of the performance of their product throughout the full length of the delivery process. Being aware of the performance of your application and taking steps not to introduce performance regressions is a continuous process. You can ensure reasonable performance at every stage of the delivery pipeline. Test proactively, rather than solve performance problems your users reported to you after the fact.
With this post, we continue the series of one-page cheat sheet for Java developers. This time we’ll look at everyone’s favourite topic, regular expressions! Often seen as the tool capable of solving almost any problem, but all too often it’s just a source of other issues.
Like many of my peers, my experience has been rooted in traditional Java web applications, leveraging Java EE or Spring stacks running in a web application container such as Tomcat or Jetty. During the 20 or so years I’ve spent as a software engineer and architect, this model has worked well for most of the projects I’ve worked on. However, recent trends in technology–among them, microservices, reactive UIs and systems, and the so-called Internet of Things (which essentially boils down to large numbers of requests from disparate devices)–have piqued my interest in alternative stacks and server technologies.
In this post, I explain how we built a simple prototype of a Vert.x server that pushes messages from a RabbitMQ queue to a browser through websockets.
We’ve gathered the data at the following services: StackOverflow, LinkedIn, GitHub, and Google search, and unified it through a simple, but effective ranking formula. And we rank some of the most prominent Java web frameworks according to this popularity index.
Last week we published a short Java challenge that required you to make javac generate the smallest Java class possible.
It got a pretty good response, quite a few of the readers decided to stretch their javac knowledge and try their hands on the challenge.
In this post, I’d like to show you a couple of solutions that I got from our readers.
Spoiler alert! If you want to see whether you can convince javac to generate a smaller class file, this is the right time to stop reading and open your terminal.
Today, however, I’d like to pose you a code-golf like challenge:
What’s the smallest Java class you can generate using javac (any vendor, any release)?
In this post, I’ll list the libraries which we learned about in the latest Virtual JUG session: The JavaFX Ecosystem by Andres Almiray. Andres has presented on the Virtual JUG before; you might remember his excellent session on how to use Gradle effectively.
The session focused on the open source JavaFX libraries that offer something that you often need in a project. And it was organized by topic: layout, testing, icons, and so on. So we’ll follow that path and cover the JavaFX libraries that Andres gave a shout out to. Disclaimer, this is not the full list of the libraries in the JavaFX ecosystem! But it’s a great place to start if you’re new to JavaFX, or if you have some experience with it and want to get better.