3 ms·
Yeah this is normally why you'd use the SDK, because its just horrific when you're outside. However, having said that, compared to FAANG internal tools, its ac
by KaiserPro 4y ago
Yeah this is normally why you'd use the SDK, because its just horrific when you're outside.
However, having said that, compared to FAANG internal tools, its actually not that bad. It's at least vaguely consistent
- PartiallyTyped 4y ago> compared to FAANG internal tools, its actually not that bad It's because it is an "internal tool". All services are built on top of aws native.
- iLoveOncall 4y agoIt's the contrary. An internal service is really good and then it becomes an AWS service. I've even been in 2 teams that have tried to do that and one may succeed in a few years.
- PartiallyTyped 4y agoIn my team, all of our services are built on top of AWS.
- damacaner 4y agoI am trying to work with MWS, and AWS SDK of GoLang horribly fails when tried to use standalone (I only need the signer part), but oh my oh my. https://github.com/canercetin-randomguy/club-noira/blob/main/main.go https://github.com/canercetin-randomguy/club-noira/blob/main... This is only the auth&sign part. and it doesnt work. and it is already 150 LoC. god.
- iLoveOncall 4y ago> However, having said that, compared to FAANG internal tools, its actually not that bad. It's at least vaguely consistent Actually I find a lot of Amazon's internal tools to be a breeze to use compared to AWS. Basically all the painful Amazon-specific stuff is done for you so it makes everything very easy. Some stuff is bad obviously but what we use the most is pretty freaking good.