And this is also where you need to think about whether your data model is going to be dependent on AWS-specific features. Ever want the freedom to migrate off of AWS? That is going to be harder if your multi-tenancy has AIM as a dependency.
Be wary of any training information from cloud providers that encourages you to implement complex solutions blending multiple cloud features. They are training you to adopt vendor lock-in.
cebert · 5h ago
That’s a valid point. I believe it boils down to tradeoffs. Do you risk vendor lock-in for simplicity and ease of use, or opt for the Kubernetes route and have only dependencies you control, which gives you more flexibility or options. Both paths have pros and cons.
Be wary of any training information from cloud providers that encourages you to implement complex solutions blending multiple cloud features. They are training you to adopt vendor lock-in.