Moving our applications to the cloud has offered useful innovations and advantageous characteristics, including flexibility, dynamic scaling, and increased resiliency. However… it’s not all been sunshine and roses. Moving to the cloud can be hard and frustrating! As developers, we’re now dealing with an ever-changing and ever more complex landscape with new tools, technologies, and features to skill up on almost every week!
Innovation in the cloud-era is about driving efficiencies, agility, and greater opportunities to deploy workloads to the cloud of your choice. Join us as we explore critical challenges faced by organizations in their move to cloud-native architectures along with the innovation in Java standards, including MicroProfile and Jakarta EE, and emerging technologies that help them build and deploy their applications on any cloud, faster and with better performance.
Over the past few years, Kubernetes has matured enough to be the favorite application orchestration platform i.e. Cloud Native (Java) Application platform, but it still missed one crucial feature of in-cluster build and deploy of the applications. The missing feature made the continuous integration and deployment(CI/CD) to be less effective on Kubernetes based platforms. The market had various solutions to solve the problem but 99% of the solutions missed something — being “Kubernetes Native” and naturally built for “K(C)loud Native Applications”.
How does one choose to architect a system that has a Microservice / REST API endpoints? There are many solutions out there. Some are better than others. Should state be held in a server side component, or externally? Generally we are told this is not a good practice for a Cloud Native system, when the 12-factor guidelines seem to be all about stateless containers, but is it?
Observability is the new trending buzzword, but is it really new? You probably all have implemented some kind of observability on your application or infrastructure without labeling it as such.
Simply said, observability allows you to understand your application performance and behavior at runtime. Nothing really new, but it does it with a perspective and a depth never reached by traditional monitoring approaches so far. It may even help predict issues before they really occur.
Kubernetes enables possibilities to develop cloud native microservices or decompose traditional applications making them more technologically advanced with the help of containers. Currently, most of the Kubernetes solutions are offered on top of VMs and there is a room for further improvements. Implementing nested architecture of application containers running inside system containers opens additional flexibility of resource allocation and management, accelerates provisioning of the clusters and pods, as well as cuts the overall costs.
For the last few years the terms cloud-native and microservice architecture have been used interchangeably. However recently people have ceased to view microservices as the go-to solution for all problems, reflecting a growing maturity in our understanding of how to best take advantage of the benefits of cloud computing.
Dive into the next generation cloud native framework for running Java in microservice oriented cloud platforms. Quarkus focuses on developers and ease of use in modern serverless environments.
It is a Kubernetes Native Java framework tailored for GraalVM and HotSpot, crafted from best-of-breed Java libraries and standards.
A hands on overview of the Quarkus cloud native framework, what it brings to the Java ecosystem and what new concepts and design guidelines it introduces.