This document discusses Shakespeare's approach to microservices. It defines microservices as a software architecture where an application is composed of loosely coupled services. It outlines advantages such as independent testing, deployment and scaling of services. It provides guidelines on when to use microservices such as for applications with different development speeds or lifecycles, when developed by multiple teams, or to isolate external dependencies. Requirements for microservices include automated testing, containerization for deployment, infrastructure as code, and centralized logging and monitoring. The document recommends loose coupling between services and using asynchronous messaging or REST/gRPC for communication.

1. Shakespeare's Approach
to Microservices
Philippe Hässig

2. Zürich,Public / Philippe Hässig / Microservices 14.September2018
William Shakespeare
Playwright, Poet (c. 1564–1616)
• Managing Partner "Lord Chamberlain's Men"
• Cofounder "The Globe"
• @shakespeare
https://www.biography.com/people/william-shakespeare-9480323

4. Microservice
Microservices is a software development technique
— a variant of the service-oriented architecture (SOA)
architectural style that structures an application as
a collection of loosely coupled services.
Wikipedia

5. Zürich,Public / Philippe Hässig / Microservices 14.September2018
Advantages
• All services can be tested separately.
• Less risk during deployments. They go faster and are smaller.
• It's easier to oversee a couple of small applications then a huge one.
• Replacing a microservice with another is quite easy, as long as the interface
stays the same. Even multiple versions of the same service can be running.
Blue-Green Deployments.

6. To be or not to be?
That is the question.
When should we use microservices?

7. Different Speed of Change

8. Different Lifecycle

9. It is a wise father that
knows his own child.

10. Multiple Teams

11. Independent Scaling

12. Isolate External Dependencies
aka Facade Service

13. Multiple Consumers

14. There's place and means
for every man alive.

15. Use the right tool
for the right job

16. Zürich,Public / Philippe Hässig / Microservices 14.September2018
Requirements
Actually nothing more than usual, but ...
• Automated Tests are mandatory
• Using a container platform enables fast and easy deployments
• Using Infrastructure as Code makes things less error prone and helps
automating new setups
• Centralise Logging and Monitoring

17. Zürich,Public / Philippe Hässig / Microservices 14.September2018
Communication between Services
• Whenever possible use asynchronous Message Queues
• AMQP, MQTT
• Otherwise use RESTful APIs or gRPC calls
• If possible, store/cache needed data locally

18. Tight Coupling
😡

19. Loose Coupling
https://shakespeareillustration.org/2016/08/12/belarius-guiderius-aviragus-and-clotens-head/

20. 'Tis best to weigh the enemy
more mighty than he seems.

21. https://martinfowler.com/bliki/MicroservicePremium.html

22. An overflow of good
converts to bad.

23. Questions?