The document discusses the author's experience with microservices architecture and deployment strategies using various programming languages and cloud services. It highlights challenges such as reliability and the need for automation in testing and monitoring. The author emphasizes the importance of adapting to new technologies while maintaining service scalability.

1. velocity.conf
#velocityconf
Mateus Prado @mateusprado
microservices
architecture

2. $ whoami
Hi, i’m Mateus,
Hi! I’m Mateus,
software and infrastructure architect.
I like Java, Ruby, C, Python, Cloud and Unix.

3. common architecture

4. The Company's software.ear
packaged

5. LoC
features
sprints
team
fix
development

6. packaged
The Company’s
software.frank

8. continuous deployment

9. manual testing

10. doesn’t scale very well

11. sizing pero no mucho

12. reliability
availability

13. tough to try newer technologies

14. new devs

15. scale cube

16. microservices architecture

17. The Unix Philosophy

18. deploy

19. continuous delivery

20. what needs to be scaled!

21. easier to
maintain

22. testautomation

23. try new technologies
Python for GET /users/login in AWS Lambda
Java for POST /checkout in AWS EC2
C for GET /metrics - Google Compute Engine
.Net for GET /about-us - Azure Cloud Services

24. The Drawbacks

25. sysadmin troop.

28. iaas
chef capistrano puppet rundeck ansible juju
own scripts.

29. deploy

30. service discovery

31. log files

32. log aggregation

33. correlation ids

34. &automation
monitoring
is required

35. cloud services.
don’t use the
cloud like a
data center

37. oops.

38. Q&A
Q&A
thank you.
Twitter: @mateusprado
Gmail: mateush.prado@gmail.com