The problem developers new to open source have is joining the community, starting to contribute, and using common open-source tools. In this session, attendees will learn how to contribute and become valuable a part of any open source community. Attendees will learn soft and hard skills based on two case studies: Eclipse MicroProfile and Apache TomEE projects.
For 2 decades, Java EE has been the reference programming model for enterprise applications. With the rise of the cloud, started by Amazon in 2006, the IT landscape has changed and application needs have evolved in terms of architecture, scalability model, observability...
Should we throw away our good old Java EE applications? Are they able to evolve in this new context? How to make them cloud-ready or even better cloud-native? Do we need to switch to another technology?
1. Jakarta EE Apps and Micro profile
2. Legacy container booting style vs. Microservices
3. Micro profile for real enterprise systems - real-time and batch
4. Faster boot-up for "cloud-native" financial systems
5. Streaming architecture with microservices
Eclipse MicroProfile helps developers quickly get started cloud-native app development using Jakarta EE capabilities. But what does this really look like if you're, say, a Java developer? What else the developer joy for Java application? Quarkus not only brings a cohesive, fun to use full-stack framework by leveraging best of breed libraries likeEclipse MicroProfile you love and use wired on a standard backbone but also combining imperative and reactive codes based JVM and/or GraalVM.
Java assumed the whole computer belonged to itself, that it could consume all available memory and CPU. In this presentation, we will demonstrate the problems associated using Java for “microservices”, and how the open source ecosystem is working to insure the future of Java by being cloud first, container native, serverless focused and Kubernetes optimized. This is where GraalVM meets Quarkus (https://quarkus.io), bringing server-side and enterprise-capable Java to enable you to build truly cloud native apps.
Historically Java was able to handle the biggest enterprise problem(s) with its Write once,run anywhere(WORA) paradigm. With Cloud Native Applications grown to popularity, things like running applications as linux containers, serverless taking centre stage -- Java was pushed back by languages like golang, node.js as the forerunner to build Cloud Native Applications as they are smaller, quicker and arguably more nimble.