4 ms·
Not exactly sure what I just read. A list of statements without any real arguments or insight in why they are the best practices. I think it is very hard to ha
by bastijn 8y ago
Not exactly sure what I just read. A list of statements without any real arguments or insight in why they are the best practices.
I think it is very hard to have such a list without over-generalizing or writing a book.
The piece could use some rework. The idea is nice, a series on best practices, but the execution needs to be looked at.
P.s. AWS has a whitepaper on the subject which is an OK read for starters in the area. I would redirect any reader of this post to the collection of whitepapers by Amazon. They also have the same for security. They cover the basics.
[0] https://aws.amazon.com/whitepapers/architecting-for-the-aws-cloud-best-practices/ https://aws.amazon.com/whitepapers/architecting-for-the-aws-...
- tekkk 8y agoYeah that was really high level overview of very specific things. I'm not sure if people without any prior knowledge of aws are getting anything out of it. For those who aren't familiar with aws i would recommend using most of the fully-managed services that aws offers. Then if you think you can save a buck by running your own databases you should go start considering them. Granted some aws services are not that great like EFS - it's just useless. But still dont go crazy with optimizing your cpu cycles. Sometimes it's just better to pay some extra for not having to spend hours debugging things that are not in the core of your business.