The document discusses the success factors and challenges associated with implementing a mature microservices architecture, particularly in a cloud-native environment. It highlights common issues such as slow feature deployment and system crashes during high user demand, while emphasizing the importance of tools and practices like service discovery, centralized configuration management, and circuit breakers. The presentation aims to guide organizations towards efficient transformations by embracing cloud-native principles and addressing persistent deployment challenges.

1. TECHNOLOGY SOLUTIONS DELIVEREDTECHNOLOGY SOLUTIONS DELIVERED
Success Factors for a Mature
Microservices Implementation
Dustin Ruehle
ECS Team, Senior Cloud Architect
@DustinRuehle .
druehle@ecsteam.com .

2. About me...
With ECS Team for 9+ years

3. About me...
•My cloud-native journey began 2+ years ago
•Working with Pivotal as a trusted partner
•Pairing with large customers enabling transformation using Pivotal
Cloud Foundry
•Platform, operations, application migration/modernization
•For who:
• a very large private company,
• a near Fortune 100 company,
• and several others with a Fortune 500 average of 24

4. About me...
Custom Tile Generation in PCFMonitoring Cloud Foundry –
Learning about the Firehose

5. Do you ever feel like…

6. What is the problem?

7. What is the problem?
“Taking to long to offer new features”

8. What is the problem?
“Taking to long to offer new features”
“We get a lot of users at once during a promotion and we crash”

9. What is the problem?
“Taking to long to offer new features”
“We get a lot of users at once during a promotion and we crash”
What are some of your problems?

10. What should be our goal?

11. What should be our goal?
avoid undifferentiated heavy lifting

12. This is what I need…right?

13. Or do I need this to solve my problem?

14. This isn’t new…

15. Cloud Native
Definition
Cloud Native
DevOps
Continuous
Delivery
ContainersMicroservices

16. Do you agree?
=
Cloud Native

17. What about this?
=
Cloud Native
=

18. What is Cloud Native?
• 12 factor applications
• Microservices
• Self-service architecture
• API-Based collaboration
• Antifragility
- Matt Stine
Migrating to Cloud-Native Application Architectures

19. Why Cloud Native?
Faster, easier, safer
”Cloud Native describes the patterns of high
performing organizations delivering software faster,
consistently and reliably at scale.”
- Pivotal

20. Cloud Native why?
”Cloud Native describes the patterns of high
performing organizations delivering software faster,
consistently and reliably at scale.”
- Pivotal
Faster, easier, safer
AND IT SOLVES A BUSINESS PROBLEM

21. Random success factor…. A µS smell test
When I want to deploy this

22. Random success factor…. A µS smell test
When I want to deploy this But have to deploy all that

23. Random success factor…. A µS smell test
Not loosely coupled
When I want to deploy this But have to deploy all that

24. Random success factor…. A µS smell test
When I want to use this

25. Random success factor…. A µS smell test
When I want to use this
I have to know about all that

26. Random success factor…. A µS smell test
Not a bounded context
I have to know about all that
When I want to use this

27. Random success factor…. A µS smell test
Refactor your
Bounded context
I have to know about all that
When I want to use this

28. Your are probably doing this…
Customer
Ordering Reporting

29. Your should probably be doing this…
Customer
Ordering Reporting
CustomerPolyglot Persistence
API-Based collaboration

30. Why containers aren’t enough?
To go to prod…
• Setup non-prod env
• Develop my business capability
• Determine
• logging
• monitoring (app and where it runs)
• security
• Integrate with other services to test
• Performance test my new business capability
• Setup my prod env
• Scale up and down based on user demand
• Troubleshoot my application working with other business
capabilities
• Patch my environment – CVEs for example

31. Problems I have yet to solve…
To go to prod…
• Setup non-prod env
• Develop my business capability
• Determine
• logging
• monitoring (app and where it runs)
• security
• Integrate with other services to test
• Performance test my new business capability
• Setup my prod env
• Scale up and down based on user demand
• Troubleshoot my application working with other business
capabilities
• Patch my environment – CVEs for example

32. Easy, I’ll just create some scripts…
Create my container

33. Easy, I’ll just create some scripts…
Create my container
Deploy my app with my
container

34. Easy, I’ll just create some scripts…
Create my container
Deploy my app with my
container
Scale my app

35. Easy, I’ll just create some scripts…
Create my container
Deploy my app with my
container
Scale my app
All my other scripts

36. Now what?

37. Somebody really smart said…
“A cloud-native application is an application
that has been designed and implemented to run
on a Platform-as-a-Service installation and to
embrace horizontal elastic scaling.”
- Kevin Hoffman
Beyond the Twelve-Factor App

38. Somebody really smart said…
Hint: This is another success factor
“A cloud-native application is an application
that has been designed and implemented to run
on a Platform-as-a-Service installation and to
embrace horizontal elastic scaling.”
- Kevin Hoffman
Beyond the Twelve-Factor App

39. What are the problems we are solving again?
We started with…
- Taking to long to offer new features
- We get a lot of users at once during a
promotion and we crash

40. What are the problems we are solving again?
We started with…
- Taking to long to offer new features
- We get a lot of users at once during a
promotion and we crash
Cloud Native
Helps me solve problems

41. What are the problems we are solving again?
We inherited…
• Setup non-prod env
• Determine
• logging
• monitoring (app and where it runs)
• security
• Integrate with other services to test
• Performance test my new business capability
• Setup my prod env
• Scale up and down based on user demand
• Troubleshoot my application working with other business
capabilities
• Patch my environment – CVEs for example
Helps me solve problems
We started with…
- Taking to long to offer new features
- We get a lot of users at once during a
promotion and we crash
Cloud Native

42. What are the problems we are solving again?
We inherited…
• Setup non-prod env
• Determine
• logging
• monitoring (app and where it runs)
• security
• Integrate with other services to test
• Performance test my new business capability
• Setup my prod env
• Scale up and down based on user demand
• Troubleshoot my application working with other business
capabilities
• Patch my environment – CVEs for example
We started with…
- Taking to long to offer new features
- We get a lot of users at once during a
promotion and we crash
Cloud Native
Helps me solve problems

43. A platform solved a lot…but some remain…
Problems that remain…
- How do I troubleshoot my application
working with other business
capabilities?
- How does my application know how to
connect to other applications?
- How do I manage configuration for my
application?
- How do I handle when an application I
consume behaves badly?
- How do I connect to my backing
services?

44. How can I solve these problems?
Problems that remain…
- How do I troubleshoot my application
working with other business
capabilities?
- How does my application know how to
connect to other applications?
- How do I manage configuration for my
application?
- How do I handle when an application I
consume behaves badly?
- How do I connect to my backing
services?

45. How can I solve these problems?
Hint: This is another success factor
Problems that remain…
- How do I troubleshoot my application
working with other business
capabilities?
- How does my application know how to
connect to other applications?
- How do I manage configuration for my
application?
- How do I handle when an application I
consume behaves badly?
- How do I connect to my backing
services?

46. What magic is this?

47. What magic is this?
Service Discovery - Eureka

48. What magic is this?
Service Discovery - Eureka
Circuit Breaker - Hystrix

49. What magic is this?
Service Discovery - Eureka
Circuit Breaker - Hystrix
Distributed tracing – Spring Cloud Slueth

50. What magic is this?
Service Discovery - Eureka
Circuit Breaker - Hystrix
Distributed tracing – Spring Cloud Slueth
Centralized external configuration management – Spring Cloud Config

51. What magic is this?
Service Discovery - Eureka
Circuit Breaker - Hystrix
Distributed tracing – Spring Cloud Slueth
Connect to backend services like databases and message brokers – Spring Cloud Connectors
Centralized external configuration management – Spring Cloud Config

52. Using Hystrix to Fail Gracefully
source: http://cloud.spring.io/spring-cloud-netflix/spring-cloud-netflix.html

53. Using Hystrix to Fail Gracefully
source: http://cloud.spring.io/spring-cloud-netflix/spring-cloud-netflix.html

54. Not just for Java…
resilient, scalable microservices to .NET developers

55. Not just for Java…
Service Discovery Config server Cloud Connectors
resilient, scalable microservices to .NET developers

56. Did I solve my problems?

57. Do you feel like this?

58. Or this?

59. Did I meet my goal?
avoid undifferentiated heavy lifting

60. Did I meet my goal?
avoid undifferentiated heavy lifting

61. Questions?