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.
The session will describe how to migrate an existing Java EE/Jakarta EE application to run in Kubernetes, how that application can be extended using Java microservices supporting MicroProfile. I will show how a "hybrid" application comprising Java EE/Jakarta EE components, microservices, and a shared distributed cache can be modeled and managed as a single logical application in Kubernetes to support ongoing application modernization. The session will demonstrate technologies that make such a migration possible, giving developers pragmatic approaches for evolving existing enterprise appl
For most enterprise projects, testing is not really fun. It’s boring, cumbersome, and takes time and effort — especially for distributed applications or when changes in existing functionality forces test scenarios to adapt. Still, software tests are crucial; so, how can we tackle them in an effective and productive way?
One of the most important things when building microservices for the enterprise mission critical systems
is high reliability. Even if a new deployed service has a bug,
it is required that the other services should not be affected by this bad service.
This session will provide how to build such a robust system with MicroProfile functions such as
Fault Tolerance, Metrics, and OpenTracing.
Although there are a lot of tuning knobs in Fault Tolerance (timeout, circuitbreaker, retry, fallback, and so on),
The session shows the attendees various examples of how the MicroProfile implementations can be integrated with products from the CloudNative standards. It will give them insight how microservices defined with Java and MicroProfile can use those products to make the operations of teir micro services easier.
Attendees should have a basic understanding of microservices and the challenges which come with them.
Transactions are one of the most complex and yet very important areas of computing. They can get particularly hard when the system moves to the distributed environments as almost every component in the distributed system is liable to failures. Traditional locking protocols, used in transaction solutions today, are then very prone to holding locks on resources for unnecessarily long periods. The saga pattern provides an alternative non-blocking solution with the design that allows individual parts of the transaction to commited immediately and independently.
The next generation Database Management Systems do their best to be non-relational, distributed, open-source, and horizontally scalable.
These banks are very easy and make any software engineer's job more comfortable, but the number of NoSQL databases are enormous! There are currently about three hundred non-relational databases, and that number keeps growing. The first question is: how to deal with so many databases? After all, there are several issues with this; there’s a learning curve for each new API, not to mention the vendor-lockin impact.
Jakarta EE 9 is out! This is the second release of Jakarta EE since the transition from the Java Community Process (JCP) to Eclipse Foundation. In this session, we will go through every aspect of Jakarta EE 9 and how this release lowers the barriers of entry, eases the migration and lays the foundation for a platform for future innovation.
We will also look ahead towards what future releases may bring.