Or how I learned to stop worrying and love Continuous Deployment... Presentation by Tom Wilkie on 29/09/16 at SF Microservices Meetup. In this talk I discuss the journey Weaveworks has been through building Weave Cloud, using all the laster buzzword-compliant techniques: Microservices, DevOps, Continuous Delivery, Kubernetes, Docker etc.

1. Microservices: Lessons Learned
Or how I learned to stop worrying and love
Continuous Deployment…
Tom Wilkie
Weaveworks, September 2016

3. https://github.com/weaveworks/scope

4. http://cloud.weave.works/

5. DEMO

6. ✓ Emergent Microservices Architecture
✓ Worse-is-better*
✓ Optimise for MTTR
✓ DevOps
✓ Continuous Delivery
* https://blog.acolyer.org/2016/09/15/the-rise-of-worse-is-better/

7. Emergent Microservice
Architecture

8. scope-probescope-probe
scope-app
Browser
scope-probe
Host 1 Host 2 Host 3
Scope OSS Architecture

9. Frontend (Nginx)
WeaverangAccount Service
scope-apps
The Interwebs
/api/app/*/api/user/*
scope-apps
scope-apps
App Mapper
scope-app
Frontend (Nginx)
Routed based on
credentials/identity
RDS
Instance
RDS
InstanceAccount Service
Static Content
Server
/*
Open Source
Closed Source
AWS Service
Service Architecture
~Sept 2015

10. Account Service
Frontend (Nginx)
The Interwebs
Weaverang
/api/report
Collection Service
/api/user
RDS
Instance
Users Service
Static Content
Server
/*
AWS
DynamoDB
/api/<app>/api/topology
Query Service Weaverang
/api/<app>/api/control
Control Service
Frontend (Nginx)
AWS
SQS
Frontend (Nginx)Authenticating
Proxy
Weaverang
/api/<app>/api/pipe
Pipe Service
AWS S3
Consul
Cluster
Open Source
Closed Source
AWS Service
NATS
Cluster
Service Architecture
~Jun 2016

11. OSS Scope
}
1. Incoming reports
2. Stored in memory
3. Outgoing queries
}
1. Incoming reports
2. Stored in S3 / DynamoDB / Memcache
3. Outgoing queries
Weave Cloud

12. Continuous
Deployment

13. App is developed
& tested locally
Built automatically
using CI of your
choice
Container image
pushed
automatically
Deployed
automatically using
Weave Cloud deploy
service...
...to an
Environment
of your choice
Source control Configuration as
code

15. Take aways

16. DO: Optimise for MTTR
DO: Adopt consistent architecture
patterns
DO: Continuous delivery
DON’T: Build user-specific services
DON’T: Over disaggregate services
DON’T: Build multiple services out of
the same image…

17. Questions?

18. We’re hiring!
London BerlinSan Francisco