Deploy Microservices as Containers on AWS with mu
•Download as PPTX, PDF•
1 like•208 views
Deploying microservices as containers on AWS to achieve maximum agility and cost efficiency.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Deploy Microservices as Containers on AWS with mu
Similar to Deploy Microservices as Containers on AWS with mu (20)
More from Casey Lee
More from Casey Lee (11)
Recently uploaded
Recently uploaded (20)
Deploy Microservices as Containers on AWS with mu
- 1. Deploying Microservices as Containers on AWS Casey Lee, Senior DevOps Engineer, Stelligent
- 2. www.stelligent.com 2 Workshop Goals Microservice Principles Monolith Decomposition Containers & Continuous Delivery mu
- 3. www.stelligent.com 3 Agenda 8:30 - 9:00 - Breakfast and registration 9:00 - 9:30 - Microservice principles and introduction to mu on AWS 9:30 - 10:00 - Lab 1: microservice deployment 10:00 - 10:15 - Lab 2: microservice testing 10:15 - 10:30 - Break 10:30 - 11:00 - Decomposing the monolith into microservices 11:00 - 11:45 - Lab 3: service discovery for microservices 11:45 - 12:00 - Wrap-up
- 4. www.stelligent.com 4 Workshop Goals Microservice Principles Monolith Decomposition Containers & Continuous Delivery mu
- 5. www.stelligent.com What’s wrong with my monolith? 5
- 6. www.stelligent.com DEPLOYMENT PIPELINE FEEDBACK LOOP plan monitor build test release Developers Customers Based on http://www.slideshare.net/AmazonWebServices/dvo202-devops-at-amazon-a-look-at-our-tools-processes
- 7. www.stelligent.com Team coupling affects agility Monolith Challenges 7 Code Monolith Code Code Daily Weekly Monthly
- 8. www.stelligent.com Deployment coupling affects availability Monolith Challenges 8 Code Monolith Code Code Code Monolith Code Code
- 9. www.stelligent.com How do microservices help? 9
- 10. www.stelligent.com 10 MICROSERVICES “Small, autonomous services that work together.” -SAM NEWMAN, 2014
- 11. www.stelligent.com 11 SINGLE RESPONSIBILITY PRINCIPLE “A class should have only one reason to change.” -ROBERT C. MARTIN, circa 2003
- 12. www.stelligent.com THE UNIX PHILOSOPHY “Write programs that do one thing and do it well. Write programs to work together.” -DOUG MCILROY, circa 1978 12
- 13. www.stelligent.com 13 MICROSERVICES “Small, autonomous services that work together.” -SAM NEWMAN, 2014
- 18. www.stelligent.com 18 Workshop Goals Microservice Principles Monolith Decomposition Containers & Continuous Delivery mu
- 19. www.stelligent.com How do I manage? 19
- 23. www.stelligent.com Continuous Delivery Fundamentals Continuous = Every change triggers the feedback process “If it hurts, do it more often!” -Martin Fowler, ThoughtWorks
- 24. www.stelligent.com Continuous Delivery Fundamentals Quality = Build it into the product “Cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the first place” -W. Edwards Deming
- 25. www.stelligent.com Continuous Delivery Fundamentals Automated = Releasing software should be repeatable and reliable “Deployments ought to be a boring, push- button experience” -Jez Humble
- 30. www.stelligent.com Container Benefits - Speed EC2 ECS 3 minutes 12 seconds 34 seconds
- 32. www.stelligent.com 32 Workshop Goals Microservice Principles Monolith Decomposition Containers & Continuous Delivery mu
- 34. www.stelligent.com 34 Amazon ECR Amazon ECS Amazon EC2 Amazon VPC router VPC NAT gateway Auto Scaling Application Load Balancer Elastic Load Balancing MySQL DB instance Amazon RDS AWS CodeCommit AWS CodePipeline AWS CodeBuild Amazon CloudWatch AWS CloudFormation alarm IAM rolestack virtual private cloud ECR registryEC2 compute container template
- 42. www.stelligent.com 42 Lab 1 - Spring Boot Service https://github.com/stelligent/mu-workshop-lab1
- 43. www.stelligent.com 43 Lab 2 - Test Automation https://github.com/stelligent/mu-workshop-lab2
- 45. www.stelligent.com 45 Workshop Goals Microservice Principles Monolith Decomposition Containers & Continuous Delivery mu
- 46. www.stelligent.com How do I decompose my monolith? 46
- 47. www.stelligent.com 47 The Challenge User Experience Business Services Data Access Layer From thick, layered architecture To small, autonomous services
- 48. Decomposition Process • Start with functionality and capabilities, NOT the data. • Look at capabilities outside in. Model services from customer perspective. • Avoid anemic CRUD services. 1. Capabilities Decomposition 2. Data Decomposition 3. Deployment Decomposition • The capabilities drive the data decomposition. • Additional services based on data access decomposition • Data needs to be owned exclusively by SINGLE service • Separating services into distinct deployables • Expose APIs • Decide on integration methods
- 49. Step 1 - Capability Cohesion Code Order Code Monolith ServiceMonolith Service Customer Code Monolith DB Monolith DB 49
- 50. Bounded Context Factor out Bounded Context into separate packages
- 51. Finding Seams “A seam is a place where you can alter behavior in your program without editing in that place.” -Eric Evans, Domain-Driven Design
- 52. Finding Seams
- 53. Finding Seams
- 54. The Anti-Corruption Layer Pattern Order Microservice Account Microservice Shipping Microservice Monolith Database Monolith Application Order ACL Account ACL Shipping ACL Application Layer Data Access Layer DAO Layer, etc. json xml json java xml csv • Each Anti-Corruption Layer (ACL) – Translates from New Domain Model to Monolith Domain Model – Prevents corruption of either domain model – Often implemented using the Façade and/or Adapter pattern – Can be built inside or outside the monolith
- 55. Step 2 - Data Cohesion Order Code Monolith Service Customer Code Order Code Monolith Service Customer Code Monolith DB Order DB Customer DB 55
- 56. Encapsulate Data Foreign Key? Use the service to access data Order Order DB Customer DB Order Customer Order DB Customer DB
- 57. Encapsulate Data Shared Data? Create a 3rd service Address Order Customer
- 58. Encapsulate Data Single Table? Split table into two Order Customer
- 59. Event Based and Eventual Consistency Order Customer Customer DB Topic Order DB POST /Orders (including address change)
- 60. Step 3 - Deployment Cohesion Order Code Microservice Customer Code Order DB Customer DB Order Code Monolith Service Customer Code Order DB Customer DB Microservice 60
- 62. Separate Deployments Independent CD Pipelines Compile Unit Test Package Deploy E2E Test ProdOrder Compile Unit Test Package Deploy E2E Test ProdCustomer Contract Tests
- 63. www.stelligent.com How do I integrate these services? 63
- 64. www.stelligent.com Database Integration Anti-pattern Order Customer Customer DB • Tight coupling – DB changes require changes in both services. • Weak Cohesion – Customer DB code exists in multiple places. • Availability – High DB load from one service will impact the other service. The benefits… The challenges… • Simple – Seems easier and quicker to start.
- 65. www.stelligent.com Synchronous Integration Order Customer Customer DB • Loose Coupling – Customer service can change independent from Order service. • Strong Cohesion – Customer DB code exists in one place. • Strong Consistency – Order service can react to downstream failures. The benefits… The challenges… • Availability – Care must be taken to avoid cascading failures (circuit breakers) • Contracts – API contract changes must be versioned to maintain loose coupling.
- 66. www.stelligent.com Synchronous Integration Order Customer Customer DB 2 Versioned API • Decouple Change • Single Deployable 1
- 67. www.stelligent.com Synchronous Integration Order Customer Customer DB Circuit Breaker • Degrade Gracefully • Shed Load • Recover Quickly
- 68. www.stelligent.com Asynchronous Integration Order Customer Customer DB Queue Dead Letter Queue • Handle Downstream Failures • Restore Consistency Dead Letter Queue Cleanup Job
- 69. www.stelligent.com Event-driven Architecture Order Customer Customer DB • Loose Coupling – Customer service can change independent from Order service. • Strong Cohesion – Customer DB code exists in one place. • Availability – Order service is not impacted by Customer service degradation. The benefits… The challenges… • Eventual Consistency – Care must be taken to achieve consistency in failure conditions • Contracts – API contract changes must be versioned to maintain loose coupling. Topic
- 71. www.stelligent.com HATEOAS Order Customer • Loose coupling – Customer service URLs can change without changing client App. The benefits… The challenges… • Complexity – Requires discipline to enforce link traversal in clients. Client App 1) GET /orders/123 2) Order (with Customer link) 3) GET /customers/456
- 72. www.stelligent.com Lab 3 - Service Discovery 72 https://github.com/stelligent/mu-workshop-lab3
- 73. www.stelligent.com 73 Summary Microservice Principles Monolith Decomposition Containers & Continuous Delivery mu
- 74. www.stelligent.com 74 Next Steps • Try mu - https://getmu.io/ • Get support - https://gitter.im/stelligent/mu • Contribute - https://github.com/stelligent/mu/blob/develop/CONTRIBUTING.md
- 75. www.stelligent.com Resources • Building Microservices, Sam Newman - http://shop.oreilly.com/product/0636920033158.do • The DevOps Handbook, Gene Kim/Jez Humble/Patrick Debois/John Willis - http://itrevolution.com/devops-handbook • mu - https://getmu.io/ 75
- 76. For more information on how Stelligent can help you with AWS Automation, go to www.stelligent.com Q&A
Editor's Notes
- add test to the pipeline