To Kate’s point of the value of sometimes taking a step back reducing features. Look at a AWS Lambda written in Java and a spring boot app. So much dependencies and libraries removed. The code becomes simpler, more explicit and the entire footprint is reduced. Less is more both in app and in database.
Exactly - the simplification mindset totally applies both ways! As Kate mentioned, AWS deliberately (we think, at least) stripped down DSQL to push developers toward simpler, cleaner database patterns. For apps that need massive scale but can live without fancy DB features, going minimal makes a lot of sense.
![AWS security breaches: Detection, response, and prevention [#125]](http://i.ytimg.com/vi/9oNYo_Blkyo/mqdefault.jpg)
![AWS security breaches: Detection, response, and prevention [#125]](/img/tr.png)
![Amazon Aurora Deep Dive: Design, migration from RDS, and cost optimization [Cloud Masters #115]](http://i.ytimg.com/vi/Owmx40o3Gkw/mqdefault.jpg)
![Amazon S3 Tables explained: Better storage for AWS Analytics workloads [#126]](/img/n.gif)
Thanks for the great discussion
Appreciate you for listening! If there are other topics you'd like to see us cover in a future episode, let me know here :)
Yay cloud masters is back! 🎉
To Kate’s point of the value of sometimes taking a step back reducing features. Look at a AWS Lambda written in Java and a spring boot app. So much dependencies and libraries removed. The code becomes simpler, more explicit and the entire footprint is reduced.
Less is more both in app and in database.
Exactly - the simplification mindset totally applies both ways! As Kate mentioned, AWS deliberately (we think, at least) stripped down DSQL to push developers toward simpler, cleaner database patterns. For apps that need massive scale but can live without fancy DB features, going minimal makes a lot of sense.