5 ms·

Without addressing deployment canaries, exponential deployments, exponential rollbacks, traffic steering, API load duplication to staging, IaaS/PaaS, 12factor a

Without addressing deployment canaries, exponential deployments, exponential rollbacks, traffic steering, API load duplication to staging, IaaS/PaaS, 12factor apps, HA, scaling, fault injection, hot backups, cold (and tested) backups, DR/BCP, configuration management, CI/CD, monitoring, troubleshooting the entire stack, and SLAs, it doesn't seem to me like a professional-enough treatment to celebrate.

andkon 5y ago
Also it would be nice if this book could do all the deploying for me.
padthai 5y ago
I have not read all the book yet, but it definitely talks about some of these things (12factor app, canaries, scaling, logging, etc.). It is a review of the most fundamental tools and strategies in Red Hat flavored Linux distros. Things like troubleshooting the entire stack would be far too advanced and specific.
tkiolp4 5y ago
I got the impression that the book is oriented to solo entrepreneurs building their own Saas (perhaps I got that wrong). What you have described sure sounds like good standards to follow by an entire infrastructure team, but a bit too much for solo devs doing infra stuff.
- chrisweekly 5y ago
  I dunno, I kinda side w the parent you replied to; it's not like 12-factor app principles or CICD are only for big teams.
  - strzibny 5y ago
    I mention both, but don't go into detail. Ad 12-factor. Some makers are better off not to follow everything. For example, it's fine to use server disk space for a single server. So I don't want to include it as dogma. Ad CI/CD. You either build it yourself (and the book gives you the technical knowledge to do it) or use a vendor (GitHub/GitLab/Circle CI). I actually want to do a bit more on CI/CD, but thinking how to approach it.
- strzibny 5y ago
  This. The book was called Deployment for Makers before, but I am taking it in a more general direction now. I wrote about some of the things mentioned above, but had to choose where I spend the time (it's already a long book). There is a reason it's called "from Scratch", because I cover starting out. Some things bootstrapping startups don't need (there are only nice-to-haves). I will update and improve the text based on feedback, though (including the comment above).
tomcam 5y ago
Do you have an up-to-date reference that handles all those concerns in one place?

andkon 5y ago

Also it would be nice if this book could do all the deploying for me.

padthai 5y ago

I have not read all the book yet, but it definitely talks about some of these things (12factor app, canaries, scaling, logging, etc.). It is a review of the most fundamental tools and strategies in Red Hat flavored Linux distros. Things like troubleshooting the entire stack would be far too advanced and specific.

tkiolp4 5y ago

I got the impression that the book is oriented to solo entrepreneurs building their own Saas (perhaps I got that wrong). What you have described sure sounds like good standards to follow by an entire infrastructure team, but a bit too much for solo devs doing infra stuff.

chrisweekly 5y ago
I dunno, I kinda side w the parent you replied to; it's not like 12-factor app principles or CICD are only for big teams.
- strzibny 5y ago
  I mention both, but don't go into detail. Ad 12-factor. Some makers are better off not to follow everything. For example, it's fine to use server disk space for a single server. So I don't want to include it as dogma. Ad CI/CD. You either build it yourself (and the book gives you the technical knowledge to do it) or use a vendor (GitHub/GitLab/Circle CI). I actually want to do a bit more on CI/CD, but thinking how to approach it.
strzibny 5y ago
This. The book was called Deployment for Makers before, but I am taking it in a more general direction now. I wrote about some of the things mentioned above, but had to choose where I spend the time (it's already a long book). There is a reason it's called "from Scratch", because I cover starting out. Some things bootstrapping startups don't need (there are only nice-to-haves). I will update and improve the text based on feedback, though (including the comment above).

tomcam 5y ago

Do you have an up-to-date reference that handles all those concerns in one place?