Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I wrote a book on web application deployment

deploymentfromscratch.com

Post reply on HN
Print view View original

101–110 of 129 posts

Re: Show HN: I wrote a book on web application deployment

#101

Post by indigodaddy »

juanse wrote: post #89
sireat wrote: post #47

From the testimonial on the page: 4 CPU cores, 16 GB of RAM, and automated backups for barely €15 a month. Where can you get a VPS for so cheap, I do not think even Hetzner goes that low?

I wrote that, and I did it without being paid or having any affiliation. Just a happy customer. This is the service I use: https://www.netcup.eu , and by the way I recommended it too.

I’m a netcup.eu customer as well. Can confirm, reliable and consistent performance and the lowest prices you’re liable to find anywhere for KVM instances..

I also have BuyVM.net instances as well. They are also excellent and have been around a long time.

Re: Show HN: I wrote a book on web application deployment

#102

Post by scottcodie »

> "The physical signals in wires and the electromagnetic waves are the basic building blocks of the link layer".

> So, what is a CPU anyway? A central processing unit (CPU) is your processor (or processor core).

> Nevertheless, making a thread-safe code unsafe is more than easy and so if your application works with threads in some ways, make sure things work as expected.

Cut the filler and just say what you're trying to say.

Re: Show HN: I wrote a book on web application deployment

#104

Post by pojzon »

e12e wrote: post #90
errcorrectcode wrote: post #84

Earlier quoted context omitted.

Nginx, in 2021, really? Envoy stomps it. https://www.loggly.com/blog/benchmarking-5-popular-load-bala... Also, what about caching, a-la at the top varnish, redis/memcache in the middle, and database tuning in the BE?

Interesting about the total requests, but the article does not test.. balancing load? In a perfect world, 1 lb in front of 4 app servers should be able to serve 4x the requests as 1 lb in front of 1 app server. So I'd imagine 4x nginx back-end servers, and a baseline hitting 1 nginx directly? That, and the fact that the nginx config is shorter, and the performance not terrible (though terrible next to envoy in this t…

Its not, its still widely used also in kubernetes world.

Tho a lot of traction is going for apps written in GO. Which supposedly makes them faster.

Re: Show HN: I wrote a book on web application deployment

#105

Post by surajs »

throwaway984393 wrote: post #99

I would not suggest this book to people who want to practice professional software deployments in 2021. This book is setting you up with a limited set of skills that are over-complicated and not best practice. For instance: Server configuration. You should not be monkeying around with OS configs. If you do, it should only be in something like a Docker container, which is an easily tested/updated versioned immutable r…

what would you recommend in its stead? for a similar audience

Re: Show HN: I wrote a book on web application deployment

#106

Post by chrisweekly »

tkiolp4 wrote: post #94
errcorrectcode wrote: post #83

Earlier quoted context omitted.

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.

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.

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.

Re: Show HN: I wrote a book on web application deployment

#107

Post by jalino23 »

throwaway984393 wrote: post #99

I would not suggest this book to people who want to practice professional software deployments in 2021. This book is setting you up with a limited set of skills that are over-complicated and not best practice. For instance: Server configuration. You should not be monkeying around with OS configs. If you do, it should only be in something like a Docker container, which is an easily tested/updated versioned immutable r…

thank you so much for this!

Re: Show HN: I wrote a book on web application deployment

#108

Post by strzibny »

tkiolp4 wrote: post #94
errcorrectcode wrote: post #83

Earlier quoted context omitted.

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.

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.

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).

Re: Show HN: I wrote a book on web application deployment

#109

Post by strzibny »

chrisweekly wrote: post #106
tkiolp4 wrote: post #94

Earlier quoted context omitted.

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.

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.

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.

Re: Show HN: I wrote a book on web application deployment

#110

Post by strzibny »

errcorrectcode wrote: post #84
strzibny wrote: post #72

Earlier quoted context omitted.

I talk about some of it (like push vs pull approach to server configuration, containers or not, single server or not), but most likely not to the extend you are probably thinking of. As for high availability I discuss whether it's worth it or not in the Scaling chapter. I also show how to use NGINX as a load balancer. I currently don't have HA content written for PG and Redis, but there are planned (as a free update)…

Nginx, in 2021, really? Envoy stomps it. https://www.loggly.com/blog/benchmarking-5-popular-load-bala... Also, what about caching, a-la at the top varnish, redis/memcache in the middle, and database tuning in the BE?

Yes, because:

1. It's popular and well understood.

2. It's included in the distribution and enjoys security fixes.

3. It's included in the distribution and shipped with good SELinux profile.

4. Since I use it to explain reverse proxy, I don't have to go into explaining new syntax (and people don't have to learn two different tools just for the sake of it).

Most people will prefer the reasons above to a better performance in theory (in theory, because I doubt NGINX will be your bottleneck).

Post reply on HN