> Small databases can be stored on a file system, while large databases are hosted on computer clusters or cloud storage. The design of databases spans formal techniques and practical considerations, including data modeling, efficient data representation and storage, query languages, security and privacy of sensitive data, and distributed computing issues, including supporting concurrent access and fault tolerance.
SlateDB delegates all of this to the object storage behind it. (I don't mean it in a disparaging way at all, just a fact)
That’s like saying Postgres delegates all this to the file system behind it. Neither a file system or S3 provide writer fencing, indexed range queries, batched/paged IO, or fine-grained data model.
> Small databases can be stored on a file system, while large databases are hosted on computer clusters or cloud storage. The design of databases spans formal techniques and practical considerations, including data modeling, efficient data representation and storage, query languages, security and privacy of sensitive data, and distributed computing issues, including supporting concurrent access and fault tolerance.
SlateDB delegates all of this to the object storage behind it. (I don't mean it in a disparaging way at all, just a fact)