> I'd love to be able to have a "relational database" that is also some "NoSQL" databases (since there's a few major useful paradigms there) that just takes care of this for me. I imagine I'd have to declare my schemas, but I'd love it if that's all I had to do and then the DB handled keeping sync and such.
You might be interested in what we're building [0]
It synchronizes your data systems so that, for example,
you can CDC tables from your Postgres DB, transform them in interesting ways,
and then materialize the result in a view within Elastic or DynamoDB
that updates continuously and with millisecond latency.
It will even propagate your sourced SQL schemas into JSON schemas,
and from there to, say, equivalent Elastic Search schema.
You might be interested in what we're building [0]
It synchronizes your data systems so that, for example, you can CDC tables from your Postgres DB, transform them in interesting ways, and then materialize the result in a view within Elastic or DynamoDB that updates continuously and with millisecond latency.
It will even propagate your sourced SQL schemas into JSON schemas, and from there to, say, equivalent Elastic Search schema.
[0]: https://github.com/estuary/flow