GreatLearning Webinar - Microservices and Event-Driven Architecture.pdf
0 likes69 views
The document outlines the principles of microservices and event-driven architecture on AWS, highlighting the differences between monolithic and microservices architectures. It discusses the benefits and use cases of microservices, including scalability, resilience, and independent deployment, and provides insights into AWS services that support these architectures. Additionally, it includes demos and references for further exploration of serverless computing and microservices patterns.
GreatLearning Webinar - Microservices and Event-Driven Architecture.pdf
- 1. Microservices and Event-Driven Architecture on AWS Dhaval Nagar 12x AWS Certified, AWS Serverless Hero
- 2. ● 12x AWS, 2x GCP, Kubernetes, Docker Certified ● AWS Serverless Hero - 2020 ● AWS Certification Subject Matter Expert (SME) ● AWS User Group Leader, Surat ● Founder - AppGambit (AWS Consulting Partner)
- 3. Agenda ● Introduction to Event-Driven Microservices ● AWS Services ● Demo (3 Demo Services) ● Q / A ● Summary
- 4. The microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API.
- 5. Characteristics of a Microservice
- 6. What is Monolithic Application ● The whole application is built as a single unit ● Often divided in three main parts ○ Client-side application (consisting of HTML pages and javascript running in a browser) ○ Server-side Application (Business or Controller Layer) ○ Data (Database) Layer (consisting of many tables inserted into a common, and usually relational, database management system) ● The server-side application will handle HTTP requests, execute domain logic, retrieve and update data from the database, and select and populate HTML views to be sent to the browser. ● This server-side application is a monolith - a single logical executable. ● Any changes to the system involve building and deploying a new version of the server-side application.
- 7. What is the use case for Micro-services ● Monolithic application are not necessarily BAD ● It largely depends on the kind of the application, team size and number of other factors like Performance and Scaling ● If you have just one application, your whole team is making code changes in that ● Test cycles can be longer ● Scaling will have to consider the whole application, even though there are only a few parts that requires more processing power
- 8. Monolithic vs Microservice Architecture https://martinfowler.com/articles/microservices.html
- 9. Microservices != Containers (Docker) ● Containers is a (Packaging and) Delivery Mechanism ● Microservice is an Architectural Pattern
- 10. 12 Factor App - Software As a Service ● Codebase in Version control ● Explicitly declare Dependencies ● Store configurations in environment ● Backing services as attached resource ● Build, Release, Run ● Stateless processes https://12factor.net/ ● Export services via Port Binding ● Scale out via the process model ● Scale fast and shrink gracefully ● Keep Dev, Staging, and Production environment similar ● Treat logs as Event stream ● Run admin processes separately
- 11. Microservices and AWS ● Compute ● Storage ● Database ● Networking and Service Discovery ● Messaging ● Logging and Monitoring ● Developer Tools
- 12. Microservices and AWS ● Compute ○ EC2 - Virtual Machine ○ ECS - Container Service ○ Lambda - Serverless Service ● Storage ○ S3 - Object Storage ○ EFS - Network File Storage ● Database ○ DynamoDB - NoSQL Database ○ RDS, Aurora - SQL Database ● Networking ○ Application Load Balancer ○ API Gateway - Managed API Proxy ○ AppSync - Managed GraphQL ● Service Discovery ○ Cloud Map - Service Discovery ● Messaging ○ SQS - Message Queue ○ SNS - Hyper scale Pub/Sub ○ EventBridge - Cloud Event Bus ○ Kinesis - Data Streaming ● Logging and Monitoring ○ CloudWatch - Distributed Logging ○ X-Ray - Distributed Tracing ● Developer Tools ○ ECR - Container Repository ○ CodeBuild - ○ CodePipeline -
- 13. Half of new apps built inside of Amazon this year are using Lambda! @ re:Invent 2020, Andy Jassy, ex-CEO, AWS https://aws.amazon.com/blogs/aws/reinvent-2020-liveblog-andy-jassy-keynote/
- 14. ● Upload functions and attach Triggers ● When Trigger runs, Lambda Service executes the Function ● You can run thousands of functions in parallel Why Use Serverless!! ● No Server Management ● Flexible Scaling ● Highly Available ● Pay for Consumption ● Secure Environment Lambda Service - Event-Driven Compute
- 15. Serverless Web Application Web App is hosted on S3 APIs managed with API Gateway Data stored on DynamoDB
- 16. How Lambda (Serverless) Works!
- 19. Serverless Microservice Patterns at AWS
- 22. Strangler Pattern - Route requests to Old and New Applications
- 23. Common APIs - Integrating different microservices
- 24. Q / A
- 25. Demo #1 - Deploy Sync/Async HTTP(S) APIs https://github.com/AppGambitStudio/GreatLearning-Serverless-Demos
- 26. Demo #2 - Process Data Files on S3 Asynchronously https://github.com/AppGambitStudio/GreatLearning-Serverless-Demos
- 27. Demo #3 - Process Data updated in MongoDB Atlas https://github.com/AppGambitStudio/GreatLearning-Serverless-Demos
- 28. When to (Not) Use ● Strong module boundaries - Focus on business features ● Independent Deployment - Adhere to DevOps practice ● Technology Diversity - Polyglot Tech Stack ● Distribution - Everything is distributed ● Eventual Consistency - Everything is distributed (again) ● Operational Complexities - Monitoring distributed resources are hard
- 29. Summary ● Almost every popular service that you know uses Microservice pattern ● Reusability across business ● Adds resiliency into the whole application ● Simple to Deploy ● Easy to Scale ● It’s not a silver bullet - may not be required in every use case
- 30. Summary
- 31. Q / A
- 32. References ● Serverless Framework - http://serverless.com/ ● AWS Serverless Application Model - https://aws.amazon.com/serverless/sam/ ● AWS Event Driven Architecture - https://aws.amazon.com/event-driven-architecture/ ● Serverless on AWS - https://aws.amazon.com/serverless/ ● Serverless Blogs - https://serverlessland.com/ ● Serverless Framework vs SAM - https://www.serverless.com/learn/comparisons/