You don't encrypt, just leave your data where it is, what we need is a live connection, after loading your data in our distributed cluster in cloud, we have option to encrypt the data for further security if needed. So yes, we encrypt at our end if asked.
Our API service doesn't store data, only load them into distributed memory for computing and API serving.
Let me know if you're interested in this API service, would like to see if we can help.
Our API service doesn't store data, only load them into distributed memory for computing and API serving.
I think you're suggesting that a queryable in-memory cache isn't storage. I don't understand that. What is it if it's not short term, non-canonical storage?
Fundamentally they both need to do computation to answer query, but they are very different, a couple of highlights:
1. API service invest a lot on reliable data ingestion/loading for users, you specify data spec, data will be served with lease term reliably. It takes care of all the data sync maintenance for you.
2. It works seamlessly with real-time streaming such as Kafka for RTA. PG is not suitable for this.
3. It's distributed nature + In-memory store guarantees low-latency API service.
Hope this describes a reasonable overview to think of it.
It's worth checking out Tinybird (https://www.tinybird.co/) if you haven't seen them. Might give you some ideas.