4 ms·
Sounds like a federated query engine with a cost based optimizer. I worked for a company that went pretty far down this path using another database. Definitel
by sixdimensional 5y ago
Sounds like a federated query engine with a cost based optimizer. I worked for a company that went pretty far down this path using another database.
Definitely a lot of potential, and also a lot of potential gotchas.
Translating from one SQL syntax (e.g. Postgres) to others, while maintaining the full capability of the other system, for example, turned out to be quite complex (but doable).
Will be following your project and wish you all the best. I suspect if you keep things sharp/focused and don't go too crazy with promises or uses cases, this could be quite successful.
Is this going to stay an intelligent router and sort of proxy? Or do you have plans for federated, heterogeneous joins, for example?
That's where things get interesting :) I think there's a lot you can do without even having to go that far.