<p>When you run your cloud native Java applications which use Jakarta EE and/or MicroProfile technologies,<br />
it makes sense to use container platform such as Docker or Kubernetes.<br />
However, there are some pitfalls on running Java applications on containers,<br />
especially when you migrate your Java applications from on-premises to containers.<br />
Unless you provide the proper settings for both Java applications and containers,<br />
IoT, virtual reality, blockchain, AI and machine learning are the software solutions of the future. All of these apps produce and consume tons of data. The amount of data is now exploading lika a data big bang. Two factors are most critical for all of these apps: best possible performance, and lowest data storage costs. Today's database systems struggle to keep pace, are very expensive in the cloud and challenging with cloud-native microservices and serverless architectures.
So, you need to have your Java app deployed and available for your users fast, and you would like to do as little managing, wiring, and infrastructure work as possible. How can you achieve that? Well, you go serverless with your containers using supersonic Java in the Cloud!
Join us exploring the possibilities with MicroProfile and Quarkus on Google Cloud Run. Bleeding edge Java!
Scared of the bleeding edges, or vendor lock-in? Don’t worry, with MicroProfile, you can switch to another app server with no changes to your code.
Let's take a look how CDC(Change Data Capture) can be done with triggers and message queuing service built directly in the Oracle Database and how easy it is to integrate it with MicroProfile Reactive Messaging. We will create Always free instance of Oracle Database in Oracle Cloud(OCI), setup simple data capture with triggers and build in queuing and consume the data with MicroProfile Reactive Messaging AQ connector in Helidon.
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.
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.