3 ms·

I've been in the industry for 20+ years. My opinion is that the extra complexity that comes from containarization is not necessary at many of the early startups

I've been in the industry for 20+ years. My opinion is that the extra complexity that comes from containarization is not necessary at many of the early startups. The benefits are not needed and the costs are hard to see but non-trivial. The companies I worked with either were slowly moving towards containarization, or were already there before I joined. I always thought that it is premature. My pet projects never used it, and I had well-running pipelines, zero-downtime, and 1-click deployments. I asked the question because I feel that I may be missing something. Perhaps the world moved on and I'm a curmudgeon, screaming at all the container-kids to get off my lawn. I recently started a little project and realized that I am not aware of what the current best practices around CI/CD are if you want to go down the route of "no containers, for now". I'm also at a point where I may be starting a new bigger project and would like to make sure I am putting in modern infra, but not necessarily pre-building and pushing containers to production.

logicalmonster 3y ago
A lot of "best development practices" exist as ways to ensure that multiple developers can all easily pickup a new project and collaborate on it successfully without conflicts. Yeah, go hog-wild and do whatever makes you happy as a solo act, so long as you do things securely and protect your users. By definition, there's no conflict between developers possible. You might pay a price later if you do things your way and get too successful, but that's a better problem to have than being too late to market with your great idea just because you were trying to do things "the right way".
screwturner68 3y ago
I almost never see CI/CD and less than 50% use containers and I'm at a different site every few weeks. That said maybe it's because I deal with highly regulated companies that don't like change and large entities where doing anything can take months so the idea of spinning vms up and down at will is not really needed or allowed. This is just what I see, not saying it's a trend, just what I see.

logicalmonster 3y ago

A lot of "best development practices" exist as ways to ensure that multiple developers can all easily pickup a new project and collaborate on it successfully without conflicts. Yeah, go hog-wild and do whatever makes you happy as a solo act, so long as you do things securely and protect your users. By definition, there's no conflict between developers possible. You might pay a price later if you do things your way and get too successful, but that's a better problem to have than being too late to market with your great idea just because you were trying to do things "the right way".

screwturner68 3y ago

I almost never see CI/CD and less than 50% use containers and I'm at a different site every few weeks. That said maybe it's because I deal with highly regulated companies that don't like change and large entities where doing anything can take months so the idea of spinning vms up and down at will is not really needed or allowed. This is just what I see, not saying it's a trend, just what I see.