How do you deploy in 10 seconds?

paravoce.bearblog.dev How do you deploy in 10 seconds?

This post describes my lessons learned after 10 years running production environments in sizes ranging from "just getting started" to a "Series F" company wi...

Hi friends, as promised, I'm back with my second post. I'll be hanging around in the comments for any questions!

In this post, I take a look at a typical deployment process, how long each part of it takes, and then I present a simple alternative that I use which is much faster and perfect for hobbit software.

Lobste.rs @lemmy.bestiver.se

How do you deploy in 10 seconds?

paravoce.bearblog.dev /how-do-you-deploy-in-10-seconds/

0 0

Selfhosted @lemmy.world

How do you deploy in 10 seconds?

paravoce.bearblog.dev /how-do-you-deploy-in-10-seconds/

13 4

Linux @lemmy.ml

How do you deploy in 10 seconds?

paravoce.bearblog.dev /how-do-you-deploy-in-10-seconds/

28 6

You're viewing a single thread.

10 comments

Your proposed solution to overly complex systems seems to be to ignore the requirements that make them complex in the first place. If that works for you, this is a perfectly fine approach. But most companies with actual signed SLAs won't accept "we'll just have a few seconds of downtime/high latency every time a developer deploys something to production #yolo".
- Also, series F but they're only deploying on one server? Try scaling that to a real deployment (200+ servers) with millions of requests going through and see how well that goes.
  And also no way their process passes ISO/SOC 2/PCI certifications. CI/CD isn't just "make do things", it's also the process, the logs, all the checks done, mandatory peer reviews. You can't just deploy without the audit logs of who pushed what when and who approved it.
  
  You're not wrong, but not everything needs to scale to 200+ servers (...arguably almost nothing does), and I've actually seen middle managers assume that a product needs that kind of scale when in fact the product was fundamentally not targeting a large enough market for that.
  Similarly, not everything needs certifications, but of course if you do need them there's absolutely no getting around it.
  
  For sure, in PCI environments this doesn’t work. And in the Series F company we don’t use this approach for that very reason. But there’s tons of companies that don’t have or need external certifications, and it works for that much more common scenario. For the small web (i.e. most of the web), it’s ideal.
  The important takeaway isn’t “wow, doing production builds on your PC isn’t secure.” Do it on a dedicated box in production, then. The important takeaway is there’s a mountain of slow things (GitHub workers, docker caching, etc) which slow developer velocity, and we should design systems and processes which remove or eliminate those pains.

10 comments