2 Sebastian Daschner • Lead Java Developer Advocate @ IBM • Consultant, trainer, book author • JCP Expert Group member & Jakarta EE Committer • Java Champion • Oracle Developer Champion (Alumni) • JavaOne Rockstar speaker
4 Java Enterprise today ● Still widely used in enterprises ● Known APIs & great developer experience ● Missing parts in a cloud-native, microservice world
10 Java EE plus MicroProfile ● Proven technology, known APIs ● MicroProfile projects fills the gaps ● E.g. Java EE plus MP Config, Fault Tolerance, Metrics, OpenTracing
14 Customizing the runtime ● Only including the required standards & runtime features ● Required? ● Trade-off between time & material spent on either development or runtime ● Optimize the moving parts (deployment artifacts) first
16 Key takeaways ● Use known APIs ● Think of MicroProfile as extensions for Java EE ● Development model that fits your need on application side ● Optimize deployment artifacts before runtime
17 Future: MicroProfile as Incubator? ● Crafting vendor-independent soon-to-be standards ● Providing what's missing from future Jakarta EE ● Sharing design principles with Jakarta EE ● Defining a reasonable process
21 Thank You For Your Attention! ● sebastian-daschner.com ● @DaschnerS ● Book: Architecting Modern Java EE Applications ● https://github.com/sdaschner/coffee/tree/microservice-cloud- webinar