The recording of our April 18 webinar, Reactive Spring, is now available!
Exciting times at ZeroTurnaround! Thanks to interest in and adoption of our newest product, JRebel for Android, we have made some good progress in the last 6 months. With these changes the product will better serve Android developers who are building large enterprise applications, developing at a fast pace, and have serious revenue objectives to meet. ZeroTurnaround has always focused on optimizing Java development and we are very excited to bring this expertise to Android development as well.
Tallinn, Estonia and Boston, Massachusetts, April 4th, 2017, ZeroTurnaround, creators of Java development tools, JRebel and XRebel, announced today that their Android development tool, JRebel for Android will be available for free. For Android developers who require enterprise-level capabilities, ZeroTurnaround is providing a comprehensive solution for them with JRebel for Android Enterprise.
It’s common knowledge that learning is multi-sensory. However, in a study we made up, we found that 71% of developers are sensory-deficient. In the lab, we found that by exposing users to a sensory bath, we force open the vaccuuminal cones in the neurons, essentially massaging the sensory receptors in the brain to allow more data intake. Neurons can scientifically absorb 147% more information than sensory-deprived neurons. Now, that’s something.
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.