Cloud infrastructure
Cloud is a set of failure domains and managed primitives. Treat it as operations, not as a logo on an architecture slide.
Personal experience
At TRIKO, backend work included Google Cloud infrastructure, Redis, Memcached, and Supervisor. At Armirene and in later ProCrédito/Soga v2 work, delivery included Docker, Kubernetes, Nginx, and S3-compatible object storage. Product-level topology is TODO.
Technical perspective
The useful questions are operational: where does state live, how is it backed up, what happens when a zone is gone, and who can change IAM. Instance count is a consequence, not a design.
Managed caches and queues are still your data. Eviction policies, failover, and connection behavior leak into application design. A cache that can go empty is not a database.
Environment parity matters more than brand. If production is a cluster and development is a shared PHP host, you are testing a different system.