- Supervisor processes.
- Small process size.
- Failure friendly design.
All of which allows easy vertical / horizontal scaling, robust concurrency and scalability, and automated process management.
Seemed promising the way WhatsApp / Discord have used this. Obviously not a classic DevOps deployment or a direct competitor for Kubernetes. But doesn't disruption happen from the sidelines?
>> Each time, I scan through pages 1-10 opening any links that seem relevant by their title (~30-60 open tabs).
I then scan through the opened tabs:
1) Closing the ones that are not relevant or are mere updates (~60%)
2) Reading the ones that are super relevant immediately (~20%)
3) Saving the ones that are 'resources' for ongoing or future projects (~20%)
Hardest to keep up with #2. Reading text articles is time consuming: 3 mins / link on average.
Sending some feedback over a mailer.