Is is also okay to store big data that would otherwise go into another storage like e.g. blog-posts?
I mean the content could also be modeled as a leaf-node and not be part of the db itself. (not sure if that would be abusing the kv storage)
Is is also okay to store big data that would otherwise go into another storage like e.g. blog-posts?
I mean the content could also be modeled as a leaf-node and not be part of the db itself. (not sure if that would be abusing the kv storage)
How do you define embedded?
One of my application is a simple "blog-like" webservice where you can either use a SQLite db or Postgres.
Personally I often prefer SQLite because it doesn't need a thousand configurations and I can just migrate all the content with copying a file.
I was just curious because of your comment:
> Also in this case you are not really using it as an embedded database anymore, which is our original motivation
As by your (and mine) definition, I am indeed using it as an embedded database. It's running inside the process and storing (and persisting) blog-posts.