My lessons learned, dos and donts from breaking down monoliths. I gathered my experience on what to do before even starting. I explained hy defining real business metrics is critical and why you should assume that many Monoliths parts will stay. Of course I mentioned the Strangler Fig pattern, but went further than that!| www.architecture-weekly.com
Every day the staff and volunteers in logistical centres receive, sort, assemble, and send to the regions hundreds of tonnes of cargo containing food, hygienic products, medicines, water, bed linen and other essentials.| Ukrainian Red Cross Society
Embarking on a native port of the existing TypeScript compiler and toolset to achieve a 10x performance speed-up.| TypeScript
Worker threads#| nodejs.org
So after several years of reading oversimplified and flat out incorrect comments about threads and fibers/goroutines/async/etc and fighting this reaction: I’ve decided to write my own still-over-simplified all in one guide to the difference between a couple popular threads and fiber implementations. In order to keep this a blog post and not a novel I’m just going to focus on linux threads, go goroutines, and rust threads. tl;dr - Rust threads on linux use 8kb of memory, Goroutines use 2kb.| Posts on Words from Shane