Embed Size (px)
Citation preview
2
Thanks for joining us.
What best describes your role?
Other 15%
DevOps Engineer 12%
Platform Engineer 15%
Engineering Management 25%
Developer 33%
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
Microservices
Single Release Cycle of Monolithic Apps
Multiple, Independent Release Cycles
8
Five trends in microservices adoption
9
reliability, availability, scalability
Trend 1: The evolving role of operations.
10
reliability, availability, scalability
developer productivity
11
• dev environment
• app resilience • CD pipeline • app monitoring • canary
deployment • …
Platform Engineers: common tools & infrastructure for the rest of the dev team.
12
TODAY! 1:30pm EDT
13
Trend 2: It’s a polyglot world (and really, it always has been).
14
It’s very hard to build an effective microservices architecture with a single language stack.
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
Trend 3: The Service Mesh
17
Service Mesh
Service
Service
Service
Service
Service
Service
Resilience
Observability
Security
18
A service mesh lets services communicate with each other.
Hystrix, Ribbon, Eureka (Library approach)
AirBnb SmartStack (Proxy approach)
Envoy / Istio (Proxy)
19
A service mesh lets services communicate with each other.
Envoy / Istio
Thursday, 1pm EDT
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%
Trend 4: Open source infrastructure
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
Trend 5: Bottoms up adoption
25
“We’re going agile” “We’re adopting J2EE” “We’re adopting the cloud”
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
“This is taking forever, I’m just going to start with an empty repo.”
Wednesday, 1pm EDT
28
Thank you! And introducing Squarespace.
