3 ms·

You don't need it if you are a one-man band doing a small side project. > I spent hours setting up a simple and free continuous deployment pipeline. Commit to

You don't need it if you are a one-man band doing a small side project. > I spent hours setting up a simple and free continuous deployment pipeline. Commit to git, Semaphore CI builds the Docker image, uploads the image to a container registry, then pulls & restarts the container on my server. It’s really cool. I felt like a wizard once I got it working … and it was free! I actually sat down here to write all about how to do it yourself, until I realised how long I spent on it and how much value it delivered to my users If you have a team of some size, the time you gain over the lifecycle of the project can be very significant when you have a smoothly running automated dev/test/UA/live pipeline. > Not build the fanciest deployment pipelines, or multi-zone, multi-region, multi-cloud Nuclear Winter proof high availability setup. If your downtime can be measured in appreciable lost revenue or reputational cost, then yes, you need all of that, as well as a solid SRE or 5 to keep it all running.

sleepychu 8y ago
> Obviously if you’re FAANG-level or some established site where that 0.1% downtime translates into vast quantities of cash disappearing from your books, this stuff is all great. You have the funds to do things “right”.
- mdekkers 8y ago
  It doesn't have to be "vast quantities of cash", it only has to balance out the cost of the additional work. And reputational cost is notoriously difficult to turn into a cash value. I really have an issue with how the author presents this as a "Almost nobody needs this stuff", where the truth is that it is a lot more nuanced. I typically advise my clients what uptime will cost them extra, per "9" (as in the 5-nines), and let them make their own decisions.
- scarface74 8y ago
  You don’t have to be a FAANG. You can be a B2B startup with one or two major clients who if they see you aren’t highly available will jump ship taking a lot of your revenue with them. I’ve been in enough meetings working for small startups where our clients grilled us about our resiliency, availability, redundancy etc. and where they forced us to put our code in escrow as part of our contract.
scarface74 8y ago
If I am a one man band doing a side project, I agree. I can build my C# project locally and just deploy directly from my IDE. But as soon as one other person is involved, I’m going to setup a simple hosted CI/CD pipeline with hosted build servers.

sleepychu 8y ago

> Obviously if you’re FAANG-level or some established site where that 0.1% downtime translates into vast quantities of cash disappearing from your books, this stuff is all great. You have the funds to do things “right”.

mdekkers 8y ago
It doesn't have to be "vast quantities of cash", it only has to balance out the cost of the additional work. And reputational cost is notoriously difficult to turn into a cash value. I really have an issue with how the author presents this as a "Almost nobody needs this stuff", where the truth is that it is a lot more nuanced. I typically advise my clients what uptime will cost them extra, per "9" (as in the 5-nines), and let them make their own decisions.
scarface74 8y ago
You don’t have to be a FAANG. You can be a B2B startup with one or two major clients who if they see you aren’t highly available will jump ship taking a lot of your revenue with them. I’ve been in enough meetings working for small startups where our clients grilled us about our resiliency, availability, redundancy etc. and where they forced us to put our code in escrow as part of our contract.

scarface74 8y ago

If I am a one man band doing a side project, I agree. I can build my C# project locally and just deploy directly from my IDE. But as soon as one other person is involved, I’m going to setup a simple hosted CI/CD pipeline with hosted build servers.