Microservices and Cloud-Driven Code Simplification

Session abstract

Microservices enforce self-containment and platform neutrality. Clouds and containers come with additional constraints regarding configuration, monitoring, logging, and load balancing. In this session, the presenter codes an application with stock Java EE and presents approaches for code and bloat removal. Questions are highly welcome.


Name Title Company
Adam Bien Consultant / Contractor Adam Bien

Session Info

Experience Session type Track
Intermediate Conference Session Oracle Code: Containers, Microservices, DevOps, Databases, APIs, and more

My Notes

Only at a 🤓 conference can a speaker ask the audience: “does anyone have a USB-C to HDMI converter” and get one 😂

  • EARs have no use whatsoever anymore
  • All Microservices are WARs
  • WARs have no self developed dependencies
  • rebuilding logic is completely legal if you will be faster that way unless next bullet
  • if you need to isolate (reuse) business logic you write a new service for it and call it over http
  • black and white architecture
  • so WARs are completely decoupled from other wars

  • javadoc is not used!

  • start with concrete classes first and add abstractions later if necessary
  • system testing done by new project and version it according to the corresponding Microservice. Now you can apply all older versions for backwards compatibility

  • monitor the use cases
    • slowest method
    • how many times called
    • and stuff