3 ms·
I think it's just you, the advice in 2016 was "just throw it up on something using docker compose", "you can later expand it with Swarm". NodeJS was a common c
by dijit 5y ago
I think it's just you, the advice in 2016 was "just throw it up on something using docker compose", "you can later expand it with Swarm".
NodeJS was a common choice too.
The real problem was their lack of an upgrade path I suppose, not the tech stack itself.
I'm also guilty of doing this and I'm an ops person, if you can't keep upgrading at a decent pace then the cost of all the upgrades becomes too great to take in one chunk.
- kome 5y ago> I think it's just you, the advice in 2016 was "just throw it up on something using docker compose", "you can later expand it with Swarm". > NodeJS was a common choice too. I agree it was common and perhaps fashionable, and perhaps it made life easier, but it also added so many level of complexity and technical debt, that now are a burden. That why I say simplicity is hard, but then it pays of (perhaps).
- dijit 5y agoCompared to the standard deployment stack these days: what SSLPing was using seems extremely simple though honestly.