Divide and Conquer: Send Forth the Microservices Jennifer Reif Email: [email protected] Twitter: @JMHReif LinkedIn: linkedin.com/in/jmhreif Github: github.com/JMHReif Website: jmhreif.com 

Who Am I? • Developer + Advocate • Continous learner • Technical content writer • Conference speaker • Other: family, horses, books, cats Jennifer Reif Email: [email protected] Twitter: @JMHReif LinkedIn: linkedin.com/in/jmhreif Github: github.com/JMHReif Website: jmhreif.com 

Monolith What is it? • Functionality in single app • Intentional or morphed over time • Pros: • One-and-done • Less communication • Cons: • Find/reuse code, Implement fi xes • Resource consumption, Handle failures Photo from Google Images 

Microservices What are they? • Small applications for limited/single function • Communicate necessary data • Pros: • Independent, Small footprint • Reliable, Scalable • Cons: • Testing, communication coordination • Additional layers/operations Photo from Google Images 

Note! Monolith vs microservices • Neither solution is a silver bullet • Simplicity and complexity exist in both! • ALSO, classi fi cation of micro services varies • Scope of functionality • Async vs sync communication • Level of automation 

Layer3 - client Layer2 - API Layer1 - database Docker-compose Demo architecture Service1 Service2 MongoDB - Goodreads 

Let’s Code! 

Where to go next? What could we do? • Polyglot - data stores • Messaging (async) - Kafka • Orchestration - Kubernetes • Testing - unit and integration • Scaling and monitoring - tool suites • Deployment - cloud services 

Resources Code and learning more… • Code (level 5): github.com/JMHReif/microservices-java • Blog: jmhreif.com/blog/ • Neo4j graph database: dev.neo4j.com/aura-java Jennifer Reif Email: [email protected] Twitter: @JMHReif LinkedIn: linkedin.com/in/jmhreif Github: github.com/JMHReif Website: jmhreif.com