How not to Cloud
0 likes184 views
The document discusses problems that can occur when using automated jobs and caching solutions without proper scaling. It recommends using elasticache for caching to avoid time bombs from improperly configured automated jobs. Aurora is suggested for database needs with its ability to handle schema changes efficiently and keep readers in sync within 100 milliseconds. Cloudfront and S3 with imgix are proposed for image serving and caching to avoid deprecated crypto issues.
More Related Content
More from Infralovers (9)
Recently uploaded (14)
![phase_4_presentation[1] - Read-Only.pptx Iot](https://cdn.slidesharecdn.com/ss_thumbnails/phase4presentation1-read-only-250301195122-ec11f187-thumbnail.jpg?width=560&fit=bounds)
How not to Cloud
- 1. How not toHow not to
- 2. WhoWho
- 7. too stupid to scaletoo stupid to scale correctlycorrectly
- 8. automated jobs ->automated jobs -> time bombtime bomb
- 9. now.. lets hang withnow.. lets hang with elasticacheelasticache
- 10. no rapid deploymentno rapid deployment modemode
- 11. cache ALL thecache ALL the redirectsredirects
- 13. redis cluster &redis cluster & php 7+php 7+
- 15. turbo modeturbo mode (batteries included)(batteries included)
- 18. aurora!aurora! readers "usually much less than 100 milliseconds"
- 20. s3 + imgixs3 + imgix