Each company has large software systems that have been continuously developed over many years, and the maintenance of these systems is becoming tougher and more expensive year after year. Against the background of new architectural paradigms such as microservices, these systems should now be modern, scalable and flexible. There is hope though - you can get rid of these big, cumbersome monoliths by decomposing them down into smaller microservices.
The Java VM HotSpot is now well over two decades old. Since then, the world of software development has changed a lot. Is it time to send HotSpot into retirement? For a long time now, Oracle Labs have been working on a new compiler for the JVM, which should be polyglot and high-performance.
Yes, you read it correctly, there are alternatives. Although the top dog Spring is enjoying great popularity with Java applications, we should not forget that there are also other frameworks worth taking a look at. Here we’ll be talking about Micronaut, a relatively new framework, but one that offers some interesting features that make it a real rival to Spring, especially in the cloud environment. In this article, we will implement an application using Spring Boot and then using Micronaut. Then, we will compare the two approaches and see where each framework is superior to the other.
Anyone who has ever set up a domain with microservices already knows: APIs for service-to-service communication are of crucial importance. Since each team has its own style and implements interfaces differently, the number of various approaches tends to explode sooner or later. Defining a guideline with rules and examples right at the beginning of the project helps to guarantee consistent APIs which are as self-explanatory as possible.
Microservices lead to new challenges, making it necessary to find new technological approaches. Microservice frameworks are of course part of the solution, but they are certainly not the most important. Which technologies play a crucial role here?
In this interview, Kai Tödter emphasise that teams have to think carefully how microservices should interact with each other, like using orchestration or choreography. The services themselves should be self-contained or use resilience patterns when they need data of other microservices.
In this interview, Gil Tayar explains that building a microservices architecture from scratch is different, and easier, than taking an existing architecture and turning it into microservices.
In this interview, Daniel Bryant talks about the great power of containers, but also about the operational responsibility they demand. He looks at the high-level steps that are essential for creating an effective pipeline for creating and deploying containerized applications.
Production hates you. The machines, the networks, the very users you hope to provide a service hate you. This is reality, and it makes production a hostile battle ground. In this interview, Russ Miles will talk about the reasons and how to turn this pain to your advantages.