DevConf.US 2022

In 2008 Amazon released their death star, a very complex graph of their MicroServices architecture. Twitter and Netflix released their own versions in 2015. The complexity and interconnectedness that was shown in those graphs highlight long-running challenges in microservices development that have been killing us for 15+ years. A world where Microservices is agile and code quality meets the needs of the business sounds amazing, but in reality managing, the complexities of typical Java programming standards and techniques is challenging to say the least

Following the success of the “10 Design Tips for Microservices Developers” talk at Red Hat Summit, DevConf.us, GovLoop, and Straight Talk for Government, this session will explore 10 Design Tips for Microservices Development with Java.

In this talk, we will explore the idea that the JVM and non-traditional Java programming techniques can be used to provide a compiler enforced JVM firewall that limits the undesirable traditional broad and public access given with typical Java development. We will funnel all requests into one well-known, tested, and validated access point. This technique will limit the amount of code we write and deliver great abstractions with robust and well-tested capabilities. What we cover aligns nicely with the principles of Domain-Driven Design, allowing you to simplify the typical 100s of artifacts in each of just a few packages. This talk will also explore ideas around telemetry and reporting on throughput. We will look at test-driven development and finish up with some specific items to consider when creating your microservices using this technique.

To round out the theory an example will be used. This example saves tens of hours and many decisions on how to get started with a recommended practice and some prebuilt scaffolding.