Learning note / Reflections on my studies
AWS Cloud Services
Cloud study makes me think beyond writing an application to the environment it depends on. AWS is a useful context for asking how compute, storage, access, and operating costs fit together.
Choosing a service around the workload
I find cloud concepts easier to follow when I start with the job to be done. Storing objects, running a server, and responding to an event are different requirements, so I should not assume one service model fits them all.
The interesting part is explaining why a choice fits the workload and what responsibility still remains with the application team.
Access and cost are design questions
A service being reachable is only one part of the picture. I also need to consider who should have access, which actions they need, and what resources will continue running.
Thinking about permissions and cost together makes the environment feel like part of the design rather than a place to upload finished code.
Thinking about deployment
I use this topic as a foundation for understanding deployment decisions. My takeaway is to make the environment explainable: what runs where, what it depends on, and how someone would notice a problem.
What I take forward
- Start with the workload rather than a service name.
- Consider access and cost early.
- Make dependencies and failure signals understandable.