4 ms·

> I think what I was saying is pretty straightforward... I was asking you to give specific examples. > Perhaps there are some exceptions for very simple archi

> I think what I was saying is pretty straightforward... I was asking you to give specific examples. > Perhaps there are some exceptions for very simple architectures, as you hint. Simplicity should be the goal and the starting point.

Terretta 6y ago
S3 and DynamoDB would be the two I’d mention first (since know it or not, folks are relying on them anyway), then things like Fargate, QLDB, and PrivateLink. Agree on the simplicity point, though the key is not just simplicity for coding, or for communicating about the architecture, but emphasizing simplicity of operation and honesty at the skills, abilities, and criticality of operating and resolving things under stress. Several years as AWS CAB member show this topic is hotly debated. I think there’s this “third way”, to purposefully exploit the different DNA of the top CSPs. I choose that word “exploit” to appeal to the board room, to feel they get more than they have to pay for (which I think is true, thanks to CSPs’ focused spend). A more friendly way of putting it from CSP point of view is “leverage what we’re best at”. Rare case of genuine win-win.