What are your best practices to scale a team when it comes to working with AWS infrastructure?
Eg. what do you do when you need 2-3 devs to develop different features for same lambda?
Gut reaction: Make sure you have someone passably familiar with MS Azure and Google Cloud consulting on your design, to minimize AWS's architectural lock-in.
Since fashion and marketing are driving our industry I'm sort of even scared to come up with proposals of other clever/smart/cheap solutions. So my gut reaction to any of these (Amazon, Google, MS, Oracle ... etc) is probably similar to yours. But that is the world we live in.
2 comments
[ 3.2 ms ] story [ 179 ms ] thread