Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Facing the Challenges of Microservice Developme...

Facing the Challenges of Microservice Development in the Cloud

Sebastian Daschner

December 05, 2018
Tweet

More Decks by Sebastian Daschner

Other Decks in Programming

Transcript

  1. 1 Facing the Challenges of Microservice Development in the Cloud

    Sebastian Daschner Lead Java Developer Advocate
  2. 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
  3. 4 Java Enterprise today • Still widely used in enterprises

    • Known APIs & great developer experience • Missing parts in a cloud-native, microservice world
  4. 5 Java Enterprise: What’s missing • Resiliency • Monitoring •

    Distributed tracing • Injectable configuration
  5. 7 MicroProfile: An alternative? • Java Enterprise developer experience •

    Addresses missing parts • Enough for more complex applications?
  6. 9 Java Enterprise: Options • Java EE 8 / Jakarta

    EE only • MicroProfile 2.0 only • Java EE plus MicroProfile additions
  7. 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
  8. 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
  9. 15 Servers supporting MicroProfile • Open Liberty 18.0.0.3 • Payara

    5.184 • Tom EE 8.0 • Wildfly 14.0.1.Final
  10. 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
  11. 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
  12. 20 OpenJ9 • OSS under Eclipse Foundation • Performance optimizations

    (Start-up time, ramp-up, footprint) • Free usage & security updates • Commercial support (optional)
  13. 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