We are happy to announce our next GOTO Night, a joint meetup with Morningstar Tech Talks. This GOTO Night is one of a series of community events to take place from now until GOTO Chicago 2016. The 4th annual GOTO Chicago Conference and Workshops will take place May 23 - 26, 2016. Phil Calçado, Software Engineering Director at DigitalOcean and Reid Draper, Director of Engineering at Helium will be presenting on March 22nd, 2016 at Morningstar USA Global Headquarters. We will have pizza and drinks at 5:15 PM and the talk will begin at 6:00 PM - We look forward to seeing you there! Presentation - DigitalOcean: Microservices as the Cloud by Phil Calçado Most infrastructure companies use somewhat traditional process when develiping their own systems. DigitalOcean is different, we are a product-driven Cloud company, focusing on building the best developer experience. Like most product companies these days, we are doing such by quickly moving our achitechture to a service-oriented approach, based on microservices. A while ago, Martin Fowler proposed that rapud resource provisioning and application deployment are pre-requires for a microservices arquitecture. The best way to achieve these is to move to the Cloud. In fact, that is why a lot of people use DigitalOcean to build their systems! https://www.eventbrite.com/e/goto-night-with-phil-calcado-and-reid-draper-tickets-21697202918

1. DigitalOcean:
Microservices as the Cloud
Phil Calçado
@pcalcado
http://philcalcado.com

3. How this kind of talk
usually goes like…

4. Big Bad Monolith
Big Bad Database
MAGIC
Super Awesome
Microservices

5. All my stuff is W.I.P.

6. Iteration 1:
The UNIX Way

7. Big Bad Database

8. Problem:
Need more machines and
datacentres, need to scale

9. Only vertical scaling
Big Bad Database
Big Bad Database

10. Iteration 2:
Building a VPS

11. Big Bad Database
Customer Tools
Service
Internal Tools
Service

12. Problem:
VPS are so last week,
people want the cloud

13. Cloud brings even
more complexity

14. Big Bad Database
Customer Tools
Service
Internal Tools
Service

15. Big Bad Database
Customer Tools
Service
Internal Tools
Service
EVERYTHING
SERVICE
EVERYTHING
ELSE
SERVICE
ENTERPRISE
SERVICE
BUS

16. Iteration 3:
Building a Cloud

17. Building a cloud means
more servers, services,
and datacentres
i.e. more essential
complexity

18. Larger services == Larger state-space

19. Adding stuff
here is easier
than creating
a new service.
Why?
Big Bad Database
Customer Tools
Service
Internal Tools
Service

20. https://www.flickr.com/photos/photophreak/
Because

21. chef/puppet/ansible
/that-thing-on-hacker-news
can be a pain, but it’s not
the fundamental problem

22. Everything was
managed by chef.
Everything was a
Pull Request.
Everything needed
code review.

23. Everything was painful.
Everything was slow.

24. This is when I apply
my bias experience

25. Back to basics
• Rapid provisioning
• Basic monitoring
• Rapid application
deployment
http://martinfowler.com/bliki/MicroservicePrerequisites.html

26. Legacy
Services Databases
How often do they change?
Couple times per month
Couple times per year
Couple times per day

27. Legacy
Services Databases
How often do they change?
Chef for now
Chef
Something else

28. 1. Rapid provisioning
you should be
able to fire up
a new server in
a matter of
hours
what about 55 seconds?

29. 2. Basic monitoring
detecting
technical
issues but it's
also worth
monitoring
business issues

30. 3. Rapid application
deployment
you need to be
able to quickly
deploy [services],
both to test
environments and
to production

31. This is the first step…

32. …but experience tells me

33. …and next up
Pre-requisites
BFFs
Programming
Language
Thunderdome
Adopt GRPC
or thrift
Build a
services directory
Get bored and
go do something
else

34. You should consider being
part of this
http://bit.ly/do-back-end-software-engineer
Phil Calçado
@pcalcado
http://philcalcado.com