3
1 Comment

Flexible Database as a Service

I was wondering if the following idea is worth pursuing:

A Database as a Service where users define the datamodel as triples (Just like in a graph database).

If certain parts of the datamodel get queried often together there is a possibility to migrate only those parts to a more traditional database (document storage/sql) with a mouseclick, thereby trading in flexibility with performance.

The advantage is that most database designers are not able to define fixed schemas when starting off a new project/startup, resulting in quiet an overhead to decide which "tables" and attributes to create. By giving them the option to define only triples this task is put on hold until actual queries show which attributes should be indexed "together"

Looking forward to an interesting discussion

  1. 1

    I get an idea of what you are saying but not entirely since I haven't heard of "triples" before. But I'm interested to have a chat on this! I'm into databases and DBaaS

Trending on Indie Hackers
Customer acquisition when broke... 39 comments How do you read this logo? 15 comments Facebook is (becoming) the new Yellow Pages 13 comments Looking for a full stack developer 7 comments I've run 1,000+ market research surveys. Here's one of THE BIGGEST mistakes Founders make when doing market research. 2 comments I am looking for marketing/growth guy 1 comment