Architecture for the cloud
0 likes232 views
This document discusses architectural principles for cloud computing. It outlines key design principles like scalability, removing single points of failure, using databases effectively, having disposable resources instead of fixed servers, loose coupling of services, optimizing for cost, caching, and security. The main messages are that cloud architecture requires scaling horizontally, using stateless components, redundancy, and expecting infrastructure to fail while utilizing managed cloud services.
Architecture for the cloud
- 1. ARCHITECTURE FOR THE CLOUD MAŽVYDAS SKUODAS
- 2. ABOUT ME MAŽVYDAS SKUODAS @ SEO HELIS
- 3. ARCHITECTURE
- 4. ARCHITECTURE
- 5. ARCHITECTURE
- 6. ARCHITECTURE
- 7. ARCHITECTURE
- 8. ARCHITECTURE IS ABOUT INTENT, NOT FRAMEWORKS Uncle Bob
- 16. CLOUD
- 17. THE CLOUD
- 20. CLOUD VS ON-PREMISE THE CLOUD COMPUTING DIFFERENCE ▸ IT Assets Become Programmable Resources ▸ Global, Available, and Unlimited Capacity ▸ Higher Level Managed Services ▸ Security Built In
- 22. DESIGN PRINCIPLES SCALABILITY ▸ Scaling Vertically ▸ Scaling Horizontally ▸ Stateless Applications ▸ Stateless Components
- 23. DESIGN PRINCIPLES REMOVING SINGLE POINTS OF FAILURE ▸ Redundancy ▸ Detect Failure ▸ Durable Data Storage ▸ Automated Multi-Data Center Resilience ▸ Fault Isolation and Traditional Horizontal Scaling
- 24. DESIGN PRINCIPLES DATABASES ▸ Relational Databases ▸ Scalability ▸ High Availability ▸ Anti-Patterns ▸ NoSQL Databases ▸ Data Warehouse ▸ Search
- 25. DESIGN PRINCIPLES DISPOSABLE RESOURCES INSTEAD OF FIXED SERVERS ▸ Instantiating Compute Resources ▸ Bootstrapping ▸ Golden Images ▸ Hybrid ▸ Infrastructure as Code
- 26. DESIGN PRINCIPLES LOOSE COUPLING ▸ Well-Defined Interfaces ▸ Service Discovery ▸ Asynchronous Integration ▸ Graceful Failure
- 27. DESIGN PRINCIPLES SERVICES, NOT SERVERS ▸ Managed Services ▸ Serverless Architectures
- 29. DESIGN PRINCIPLES OPTIMIZE FOR COST ▸ Right Sizing ▸ Elasticity ▸ Take Advantage of the Variety of Purchasing Options ▸ Spot Instances ▸ Reserved instances
- 30. DESIGN PRINCIPLES CACHING ▸ Application Data Caching ▸ Edge Caching
- 31. DESIGN PRINCIPLES SECURITY ▸ Utilize AWS Features for Defense in Depth ▸ Offload Security Responsibility ▸ Reduce Privileged Access ▸ Security as Code ▸ Real-Time Auditing
- 32. IN SHORT ▸ Remove single point of failures ▸ Expect it to die ▸ Use as much services as possible in the beginning ▸ Stateless is a key