This document discusses microservices architecture and how it compares to monolithic architecture. It notes some advantages of microservices such as independent scalability, fault isolation and faster deployments. However, microservices also introduce more operational complexity. The document recommends Spring Boot as a solution for building microservices due to its features like embedded servers, auto-configuration and production-ready environments without XML configuration. It also describes Spring Boot Actuator which adds monitoring endpoints.

1. Microservices
w/
Spring Boot
Mesut Can Gürle

2. ● Extreme Programmer
● Open Source Enthusiast
● PhD Student
● Devops Turkey, Istanbul
Coders
● #793 @LKD
● @mesutcang
● Jedi

3. Agenda
❏ Monolithic Architecture
❏ Advantages & Disadvantages
❏ Microservice Architecture
❏ Advantages & Disadvantages
❏ Suggestions
❏ Spring Boot Solution

4. Burj Khalifa 828 m

6. Characteristics
● Large Codebase
● Many Components, no clear ownership
● Long deployment cycles

7. Advantages
● Single codebase
● Easy to develop / debug /
deploy
● Good IDE support
● Easy to scale horizontally
● Ops team can efficiently
handle

9. Problems
● As codebase increases …
● Tends to increase “tight
coupling” between
components
● All components have to be
coded in the same
language
● Scaling is
“undifferentiated”

11. Characteristics
● Many smaller (fine grained), clearly scoped services
● Single Responsibility Principle
● Domain Driven Development
● Bounded Context
● Independently Managed
● Clear ownership for each service
● Typically need/adopt the “DevOps” model

12. Unix philosophy
● Write programs that do one thing and do it well.
● Write programs to work together.
$ du | sort -nr |head -n 2 | tail -n 1

13. Why
● Faster and simpler deployments and rollbacks
● Independent Speed of Delivery
● Right framework / tool / language for each domain
● Recommendation component using Python?, Catalog Service in Java ..
● Greater Resiliency
● Fault Isolation
● Better Availability

16. Problems
● Service Discovery
● Operational Overhead
● Distributed Systems are
inherently Complex
● Service Versioning
● Testing
● Fan out of Requests

24. Why Spring Boot?
● Stand-alone Spring applications
● Embedded Tomcat or Jetty
● Starter dependencies
● Automatic configuration
● Production-ready environment
● No code generation / no XML config

26. Actuator
● Adds common non-functional features to your application and exposes
MVC endpoints to interact with them.
● Endpoints: /metrics, /health, /trace, /dump,
/shutdown, /beans Audit /info
● If embedded in a web app or web service can use the same port or a
different one (and a different network interface).

27. Questions