Similar to how in the "POSIX threads" section you indicate that pthread_create() is UNIX/POSIX-specific, you should probably indicate in the "Creating new Processes" section that fork() and execve() are Unix/POSIX-specific. That, or you could indicate that you are describing generally in that context.
In "Running multiple programs" you state: "After a few seconds, it pauses, saves the state of the RAM, and changes processes." Saying it "saves the state of the RAM" is probably not a good characterization since it is more likely just changing what memory is accessible. It is also, most likely changing the virtual memory mappings to give the illusion of using the same memory addresses (though it does not have to, for instance a system with a MPU still has a concept of distinct programs even though virtual memory mappings are not supported), but you could omit that to the later virtual memory section without being incorrect.
Yeah, I purposefully "simplified" how virtual memory works here so that the focus could be on multitasking and context switching, but agree that isn't totally accurate. I actually had hoped to do a part II on virtual memory, but we'll see if time permits that :)
Still in virtual machines, but ones with local NVMe drives rather than network-attached storage (EBS, Persistent Disk). This means incredible I/O performance.
In the database world, serverless/autoscaling pricing is almost always more expensive for real workloads. The % of workloads where it makes sense is small. Ones where 90% of the time there's little small traffic and 10% of the time the DB sees large traffic spikes. Otherwise, just pay a fixed cost for the hardware you need.
Multigres is made by the guy that made Vitess, Sugu, before it became a startup. Doesn't mean it will be better, but I think it's why people have high hopes for both products.
You forgot the read the original text above my response.
> I looked Neon recently, and it appears that it's designed as a SaaS product from the outset; while it is technically possible to self-host the individual components of the architecture, it does not look trivial, in large part because the control plane is closed source (and probably extremely specific to Neon's SaaS operations).
This is a good reason to go with multigres vs Neki (assuming Neki gets integrated into planetscale vs a standalone multigres ).
The two announcement's regarding Neki smells like its going to be proprietary or heavily tied into planetscale. See the gauging interest two months ago with sign ups. The current signing up ... Feel very marketing focused.
> Like Vitess, Multigres will be open source using the same license: Apache 2. You can follow the repo here.
We shall see, but one is running and acting like pure open source project, and another is being announced how the marketing department of a proprietary software company works.
And the timing is interesting. Coincidence that both Neki and multigres got announced right at the same time? I am suspecting there has been some background drama going on with planetscale and supabase. But that is off-topic.
Like i said, and i agree with the poster i responded too: That Neki smells like its going to be tied into planetscale.
https://www.neki.dev