In the modern world, anything that moves generates this exact type of data: where something is(space) and when it was there(time).
It could be a runner running around the city, a drone trying to deliver a product, or you wandering through a maze not knowing which direction you are running.
When you need to store this data, the conventional choice is to reach for a general-purpose relational database like PostgreSQL or an embedded store like SQLite. And for many applications, that is a perfectly reasonable choice. General-purpose databases can certainly handle high ingestion rates when tuned properly.
However, general-purpose databases are designed to support a broad range of workloads: mutable tables, random-access updates, secondary indexes, and relational joins.
potDB isn't built on the premise that general-purpose databases are inherently unsuitable.…