Hacker News Reader

Comment by toomuchtodo | Hacker News Reader

Appreciate why conservative technology choices are made when possible (pick boring tech).

Don't rush new features or code into production. Don't deploy anything after 5pm on a Friday.

Documentation, documentation, documentation. If there's a piece of knowledge for your app that's only in your head, you have failed.

View on HN

I always feel being scared of deploying on a Friday is a massive red flag that deployment proccess, does not have good automatic testing, doesn't use canaries and does not have seemless roll backs.

The Deployment is a tension point of Software Development Life Cycle[1]. The more we deploy less scared we are.

[1].:http://dl.acm.org/citation.cfm?id=2593813

Nowadays we still having the scary of deploying on Fridays. What are we missing to lose this fear? Isn't DevOps mature enough? How big enterprises like Google/Facebook/Amazon.. are handling it?

We deploy on Fridays because our app is used only from Monday-Friday and if anything goes wrong we have the whole weekend to fix it, but we've never actually had to do that.

What you think about sandbox applications (like docker) over a PaaS can it mitigate a heterogeneous scenario?

Containers almost always for local dev environments. I don't recommend containers in production unless you're going all in on a container scheduler (like Kubernetes). Without running multiple containers on the same virtual machine (and and orchestrator performing the work for you), you're adding an additional layer of abstraction with no benefit.

Thanks for the reply, but can you explain (or provide some reference) about why not to use containers-only in production?

I know that I will add a layer of abstraction, however from a Dev perspective I have some benefit like a byte-to-byte compatible test/prod env that I haven't to worry about dependencies per example.

Reply on news.ycombinator.com