Building microservices step by step and deploy in cloud run

Building microservices step by step and deploy in Cloud Run

Transcript

1. Serverless Microservices with Google Cloud Run Juan Guillermo Gómez @jggomezt
2. Juan Guillermo Gómez • Co-Leader y Co-Founder del GDG Cali. • Founder DevHack. • Tech Lead Wordbox • Consultant and advisor on software architecture, cloud computing and software development. • Experience in several languages and platforms. (C, C#, Java, NodeJS, android, GCP, Firebase). • Google Developer Expert GCP & Firebase • BS in System Engineering and a MS in Software Engineering. • @jggomez
3. WHERE ARE THE SLIDES? https://speakerdeck.com/jggomez/serverless-with-cloud-run
4. FOUNDATIONS
5. Where the microservices come from? ❖ Modular Programming. ❖ POO ❖ RPC. ❖ EAI. ❖ AOP. ❖ Web Services. ❖ SOA
6. Microservices
7. Microservices
8. Microservices
9. Microservices Process
10. ANALYSIS AND DESIGN
11. Modeling Microservices ❖ Model services around the business domain. ❖ Model services around quality attributes. ❖ Model services around cost
12. Microservices Description with Open API 3 OpenAPI Specification (formerly Swagger Specification) is an API description format for REST APIs. An OpenAPI file allows you to describe your entire API, including: ❖ Available endpoints (/users) and operations on each endpoint (GET /users, POST /users) ❖ Operation parameters Input and output for each operation ❖ Authentication methods ❖ Contact information, license, terms of use and other information. ❖ API specifications can be written in YAML or JSON. The format is easy to learn and readable to both humans and machines.
13. Microservices Description with Open API 3
14. Microservices Description with Open API 3
15. Microservices Design
16. Create Mockups
17. BUILD MICROSERVICES
18. How to build microservices ❖ Separation of concerns. ❖ Business Context. ❖ Clean Architecture.
19. Frameworks to build microservices
20. TEST
21. How to test microservices
22. DEPLOY
23. SERVERLESS ➢ Serverless architectures are application designs that incorporate third-party “Backend as a Service” (BaaS) services, and/or that include custom code run in managed, ephemeral containers on a “Functions as a Service” (FaaS) platform. ➢ Serverless architectures may benefit from significantly reduced operational cost, complexity, and engineering lead time, at a cost of increased reliance on vendor dependencies and comparatively immature supporting services. https://martinfowler.com/articles/serverless.html
24. Cloud Run ➢ Cloud Run is a managed compute platform that automatically scales your stateless containers. Cloud Run is serverless: it abstracts away all infrastructure management, so you can focus on what matters most — building great applications. ➢ Run your containers in fully managed Cloud Run, or on Cloud Run for Anthos. Anthos supports GKE on Google Cloud, on-premises and multi-cloud environments. Cloud Run is built from Knative, ensuring that your applications are built on an open standard.
25. Cloud Run - Kubernetes
26. Cloud Run https://twitter.com/ahmetb
27. Deployment
28. Cloud Run - Deploy ❖ gcloud config set project PROJECT-ID ❖ gcloud builds submit --tag gcr.io/PROJECT-ID/accountservice ❖ gcloud beta run deploy --image gcr.io/PROJECT-ID/accountservice --platform managed
29. Cloud Run - Kubernetes
30. Cloud Run - Kubernetes
31. Cloud Run - Demo https://github.com/escueladevhack/ScalabilitySoftwareArchitecture
32. CI & CD
33. Continuous Integration & Continuous Delivery
34. Continuous Integration & Continuous Delivery
35. Continuous Integration & Continuous Delivery
36. BONUS
37. BONUS
38. Proxy
39. Call a microservice to another microservice ASYNC
40. Call a microservice to another microservice ASYNC
41. Call a microservice to another microservice SYNC
42. Caching Microservices ❖ Use a memory repository for instance REDIS. ❖ Keep the data in the cache when it doesn’t change. ❖ if another component changes the data, the cache must be deleted. Queues can be the solution. ❖ Cloud run doesn’t support memory store but the cloud functions support memory store
43. Security in the Microservices ❖ Consider implementing authentication at API Gateway level with widely-used API security standards such as OAuth2 and OpenID Connect. ❖ Create a API secret for app. ❖ Security channels ❖ JWT http://kasunpanorama.blogspot.com/2015/11/microservices-in-practice.html
44. Best Practices Microservices ❖ Domain Driven Design. ❖ Decentralized Data Management ❖ Smart Endpoints and dump pipes ❖ Asynchronous Communication ❖ Avoid Coupling between Services ❖ Decentralize Development ❖ Monitoring Microservices
45. Best Practices Microservices ❖ Keep domain knowledge out of the gateway ❖ Token-based Authentication ❖ Event Driven Nature ❖ Fault Tolerance. (circuit-breaking, bulkhead, retries, timeouts, fail fast, failover caching, rate limiters, load shedders) ❖ Product Engineering
46. REFERENCES ❖ Building Microservices. Book. Sam Newman ❖ https://martinfowler.com/articles/microservices.html ❖ https://martinfowler.com/articles/serverless.html ❖ https://cloud.google.com/run/ ❖ https://medium.com/weareservian/3-best-features-of-google-cloud-run-546e367242ea ❖ https://medium.com/platform-engineer/microservices-design-guide-eca0b799a7e8 ❖ https://blog.risingstack.com/designing-microservices-architecture-for-failure/ ❖ http://kasunpanorama.blogspot.com/2015/11/microservices-in-practice.html
47. GRACIAS !! @jggomezt