Internal Developer Portals are reshaping the developer experience. What's the best way to get started? Do you build or buy? Tune in to see.
Agentic AI. It's everywhere. But what does that mean for developers? Learn to leverage agentic AI to improve efficiency and innovation.
Jakarta EE is evolving into a new world of cloud native computing, with new ways to deploy it into containers and support for working with cloud technologies. However, cloud native is about far more than just how you deploy apps. From where Jakarta EE has come, moving to the cloud is a shift from investing in big servers that can host an entire system and are supposed to always run with little to no downtime, to running on many small commodity servers that can, and do, crash all the time. Such a move requires a paradigm shift in the way we architect systems. Our old paradigm exploited ACID transactions to allow us to take consistency for granted, in our new cloud native landscape, a single operation is served by many different services and databases, rendering ACID transactions unable to offer consistency guarantees. We need a new approach to architecture, one that once again allows us to take consistency for granted, even in the face of failing services. The architecture that delivers this is streaming.
In this webinar, we'll take a look at the new Jakarta EE landscape, at how MicroProfile fits into it, and how some new specifications being created in MicroProfile are set to transition Jakarta EE architecture into a cloud native landscape. These new specifications are built on reactive principles, using Reactive Streams as a programming model and asynchronous messaging as an architectural default. We'll see these specifications demoed live, showing how they solve the problems that are introduced when you move to a cloud native deployment model.