What is io_uring. io_uring is a high-performance asynchronous I/O (Input/Output) interface introduced in the Linux kernel (version 5...

Authorisation In this section, we will cover how Authorisation works in Goiter. Every authorisation service has to deal with the following elements: - Accessor/Actor/User - Resource/Object - Action The underlying statement for an authorisation service is if an accessor should be allowed to perform an action on the resource...

Someone posted on Twitter about the exorbitant price that Zoom charges if one wants to organise a single session with more than 10,000 attendees. It's around $6000...

What exactly is the Swap Space. Linux system uses the Virtual File System (VFS) to abstract the physical memory available from the memory visible to the linux processes...

Once upon a time, I was working on an in-memory datastore and creating the memory pool for the datastore. As usual, there were multiple design ideas that people put forth to solve it...

If you have worked with distributed systems, you must have come across this famous quote: In a distributed system, the only thing two nodes can agree on is that they can't agree on anything. This quote has stuck with me because it perfectly captures the complexity of building distributed systems...

Have you ever wondered how durable are your writes. Do you expect calling fd...

This is a follow up article to [this](https://gauravsarma. com/posts/snapshotting-in-a-high-throughput-shared-nothing-database/) post that I wrote about comparing Copy on Write and Redirect on Write mechanisms...

While browsing Twitter (it will never be X. com for me), I came across a tweet where it was being discussed how an engineer from a big tech company was unable to explain how async/await works after working on a particular language for 3+ years...

Snapshotting in a high throughput shared-nothing database While working on a Golang based in-memory database, I recently had to implement point in time snapshots for the datastore. The in-memory database has a shared nothing architecture allowing it to run multiple goroutines, usually based on the number of available cores and the keys are allocated accordingly to the shard goroutines...