Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Any thoughts about maintenance? My personal journey with learning AWS is/was very painful, but now that I understand everything that I need at a high level, it is quite a bit more manageable. I can't imagine having to make minor tweaks to my infra if I had no idea what it was doing.


It's something I've been thinking about for a while.

I think it will depend on the people that will use it.

Some architecture require more maintenance than other.

For example, the first architecture that I've created is a serverless architecture based on Docker. Under the hood it only uses managed services like Fargate, CodePipeline, CodeBuild, Aurora...

Given that you'll have a catalog of different architectures, people that don't have any experience with AWS may need to choose architectures like that.

Also, each architecture contains a detailed Readme that explain the basic operations (updating ELB HealthCheck, increasing the amount of RAM that could be used by a Fargate task and so on...).

It's a complex subject, by the way, so I am entirely open to any comments, ideas or suggestions.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: