As more companies have adopted microservices, conventional wisdom on microservices architecture and best practices have started to converge. Based on Datawire's experience with dozens of companies, we’ll discuss the evolution of these key trends, including polyglot architectures, the service mesh, and the role of operations.

2. 2
Thanksforjoiningus.

3. What best describes your role?
Other
15%
DevOps Engineer
12%
Platform Engineer
15%
Engineering Management
25%
Developer
33%

4. 4
https://gitter.im/datawire/summit
#msvsummit

5. Monday, July 24
1 PM - 1:30 PM EDT Opening Keynote: Trends in Microservices Richard Li, Datawire
1:30 PM - 2:30 PM EDT Microservices at Squarespace Kevin Lynch & Doug Jones, Squarespace
Tuesday, July 25
10 AM - 11 AM EDT How to Avoid Creating a GitHub Junkyard Lauri Apple, Zalando
1 PM - 2 PM EDT
Ancestry’s Journey towards Microservices,
Containerization, and Kubernetes
Paul MacKay, Ancestry
Wednesday, July 26
1 PM - 2 PM EDT
Move fast, make things: how developers
can successfully adopt microservices
Rafael Schloming, Datawire
Thursday, July 27
1 PM - 2 PM EDT The Mechanics of Deploying Envoy at Lyft Matt Klein, Lyft

7. 7
Microservices
Single Release Cycle of
Monolithic Apps
Multiple, Independent
Release Cycles

8. 8
Fivetrendsinmicroservices
adoption

9. 9
reliability, availability, scalability
Trend1:Theevolvingroleofoperations.

10. 10
reliability, availability, scalability
developer
productivity

11. 11
• dev
environment
• app resilience
• CD pipeline
• app monitoring
• canary
deployment
• …
Platform Engineers:
common tools &
infrastructure for the rest
of the dev team.

12. 12
TODAY! 1:30pm EDT

13. 13
Trend2:It’sapolyglotworld(andreally,italwayshasbeen).

14. 14
It’sveryhardtobuildaneffectivemicroservices
architecturewithasinglelanguagestack.
Each service might be written in a single language, but the library
versions used are different
• If you try to make them the same, you end up with a distributed
monolith
Different languages are good at different things, e.g., Python for
data analysis is a common use case

15. 15
Trend3:TheServiceMesh

17. 17
ServiceMesh
Service
Service
Service
Service
Service
Service
 Resilience
 Observability
 Security

18. 18
Aservicemeshletsservicescommunicatewitheachother.
Hystrix, Ribbon, Eureka
(Library approach)
AirBnb SmartStack
(Proxy approach)
Envoy / Istio
(Proxy)

19. 19
Aservicemeshletsservicescommunicatewitheachother.
Envoy / Istio
Thursday, 1pm EDT

20. I'm running a service mesh in production
3%
I'm actively evaluating service meshes
8%
I've read about them
32% Not at all
57%

21. Trend4:Opensourceinfrastructure

22. 8%
8%
7%
19%
58%
We are not using
Kubernetes
We have a dev/test cluster for
evaluation
We have a dev/test cluster under active
use
We are running a few production
services on Kubernetes
We’re mostly running our
production on Kubernetes

24. 24
Trend5:Bottomsupadoption

25. 25
“We’re going agile”
“We’re adopting J2EE”
“We’re adopting the cloud”

26. 26
“We’re going agile”
“We’re adopting J2EE”
“We’re adopting the cloud”
“This is taking forever,
I’m just going to start
with an empty repo.”

27. 27
“This is taking forever,
I’m just going to start
with an empty repo.”
Wednesday, 1pm EDT

28. 28
Thankyou!AndintroducingSquarespace.