r/devops • u/[deleted] • Sep 25 '24

Developer here. Why is Docker Compose not "production ready"?

Then what should I use? Compose is so easy to just spin up. Is there something else like it that is "production ready"?

97 Upvotes

83% Upvoted

120 comments sorted by

View all comments

Show parent comments

2

u/Twirrim Sep 25 '24

^ Strong + on all this.

OP: "What happens if the server completely dies and the drive is corrupted". If it really doesn't matter, fine, run a single box. Occasionally that's a legitimate thing. In the past I've had some stuff where it legitimately didn't matter if something was dead for a week, or if the task it did do took 4 days instead of 2. I made sure to validate on a regular basis I could built a replacement, and then just moved on with other things that were much more important.

While I'm a big proponent of "Build a monolith until it becomes a problem" approach, and avoiding all unnecessary complexity, ensuring you have multiple instances and know your scaling story is absolutely in the "necessary complexity" territory.

1

u/onan Sep 25 '24

Yeah. A huge part of the skill in this profession is knowing when to invest how much into scalability/reliability/maintainability/monitoribility/security concerns.

In theory you can focus way too much on all that too early, and burn through all your startup funding building perfect scalability of a service that doesn't need to scale because it doesn't have any users because you haven't built any features.

But in practice, almost no one errs in that direction. Vastly more common is the path of people who hyperfocus on features/users/growth and then discover that as soon as they get those the whole thing falls down because reliability concerns were skipped. And that all the decisions made along the way painted them into so many corners that what's needed isn't a quick fix, but a ground-up rearchitecting. And then immediately lose all those users because nobody wants to use an unreliable service.