Hacker News new | past | comments | ask | show | jobs | submit login

EB is kinda a mixed bag. Is there much production on EB? It’s great for q&d stuff you don’t want to get into specifics but I couldn’t imagine explaining my architecture with a big “EB does what EB wants to do here” bubble



Notion (my employer) was 100% Elastic Beanstalk until about a month ago, now we’re 100% ECS. We migrated once our 1200 box cluster started stalling deploys randomly while saying everything was healthy in the API. At that many instances, the some pages in the dashboard would hang the browser.

One bad day, it took like 18 hours from deploy attempt started to AWS resolving the situation by fiddling knobs on their side.

Our deploys on ECS take like 15 minutes.


Did the migration went easy? We are currently running all our production service through EB as well, but we only had smaller issues (e.g. deployments stalling, health checks not working correctly etc).

Would you recommend to invest time learning how ECS works or had your company hires that managed that?


ECS and some ECS Fargate work great - I really like that combo. Seems pretty low overhead, and ECS anywhere I've had some luck with just playing around (you can do a local box on a 1Gig link with tons of RAM / Storage etc).

My one compliant is around having fallback to on-remise providers / capacity provider etc support - doesn't seem fully fleshed out across ECS/Fargate/ECS anywhere but I may not have read docs properly yet.


EB is neat when it works, but it’s only as good as it’s weakest link. I constantly get environments stuck in unavailable statuses etc. I don’t recommend it for anyone except maybe that R&D stuff. Much better to go ECS/Fargate/EKS IMHO.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: