Ask HN: What's your container story?

1) We use containers all over our process. From local development to production. In production we run in AWS ECS Service clusters with 9 containers per cluster. These are mostly rails servers and nginx reverse proxy's.

2) We run rails servers, nginx reverse proxy's, CI/CD uses containers, we have jobs for data processing that use containers. Probably other things too.

3) Things :D

4) Yes and no. We don't use orchestration tools but we do have orchestration using customer rake tests and deep integration with our CI/CD environment.

5) It's hard to hug a container... that's the biggest challenge.

1. Using containers, close to 20 of them in production. Same for homolog, and a few at a time for dev;

2. Everything: Database (CouchDB+ES), Apps(in PHP, Ruby and Clojure) and auxiliary stuff(proxy, wiki, static server, mailer...);

3. Small: 2 techs, 1k users. Biodiversity conservation in the government;

4. No orchestrators. Using docker-compose only;

5. On boarding new members that are not experienced, sometimes takes a while for the abstraction to "kick in";

Thing i want to add on usefulness: To me containers are mostly a way to abstract configuration and document it in code. Lots of server processes go into a cloud, and this can help us iterate faster in the future.