General Scenario

I am thrilled to be a part of this exciting initiative 14-week online bootcamp led by Andrew Brown in which students from around the world connect to share cloud resources, specifically those from AWS cloud provider like AWS billing, app containerization, caching, CI/CD with AWS CodePipeline, CodeBuild, and CodeDeploy, modern APIs, and IaC, to name a few.

It all begins when you walk in as a cloud engineer into a tech startup that's building an application called Crudder, which is an ephemeral platform for microblogging; it’s a social media platform with posts that have a limited time and then expire. Stakeholders hope to attract thousands of users and rapidly scale within a certain predefined budget and scope while considering the risks and rewards of adding new components and features and how they will all be balanced.

Know and understand that architecture diagrams are great to show when you are presenting your project to anybody, non-technical and technical people because for non-technical they will help them to get how much the system you're building is valuable and why it costs that budget as long the overall context should feel right to them. On the other hand for technical people, architecture diagrams define and explain a lot of complicated fragments of the heavy workload as there will be a negotiation for reaching a deeper understanding. Let's get a brief about the diagrams where conceptual diagrams are to communicate at a high level the architecture to key stakeholders. Logical diagrams communicate the broad strokes of the technical architecture to engineers. Physical diagrams communicate in detail the technical architecture for engineers when implementing the design.

For better architecture try your best to be attached to the AWS Well-Architected Framework as it helps in building secure, high-performing, efficient, and resilient infrastructure for most workloads and applications. We can't talk about the AWS Well-Architected Framework without mentioning the SIX Pillars that I abbreviated to CORPSS which are Cost Optimization, Operational Excellence, Reliability, Performance Efficiency, Sustainability, and Security.