5 ms·
What are the specific lessons worth preserving, but being lost? (I assume that "keep an image, it's too costly to rebuild everything from version-controlled so
by nine_k 2y ago
What are the specific lessons worth preserving, but being lost?
(I assume that "keep an image, it's too costly to rebuild everything from version-controlled sources" is not such a lesson.)
- igouy 2y agoYes specific would be better. Of course "keep an image" and "version-controlled sources" are not mutually exclusive. https://www.google.com/books/edition/Mastering_ENVY_Developer/ld6E19QIMo4C https://www.google.com/books/edition/Mastering_ENVY_Develope...
- swiftcoder 2y agoThe biggest common lesson is being able to inspect/interrogate/modify the running system. Debugging distributed system failures purely based on logs/metrics output is not a particularly pleasant job, and most immutable software stacks don't offer a log more than that. However, for Erlang specifically, the lesson is pushing statelessness as far down the system as you possibly can. Stateless immutable containers that we can kill at will are great - but what if we could do the same thing at the request handler level?
- tonyg 2y ago> (I assume that "keep an image, it's too costly to rebuild everything from version-controlled sources" is not such a lesson.) Exactly - that lesson is in no danger of being lost. Docker and other kinds of VM image are ubiquitous.