3 ms·

Thanks for your wishes @nishantvyas! This might help answer some of your questions: https://docs.yugabyte.com/latest/introduction/#what-are-the-trade-offs-invo

Thanks for your wishes @nishantvyas! This might help answer some of your questions: https://docs.yugabyte.com/latest/introduction/#what-are-the-trade-offs-involved-in-using-yugabyte-db https://docs.yugabyte.com/latest/introduction/#what-are-the-... Please look at the trade-offs in the above section (vs SQL, vs transactional NoSQL, vs eventually consistent NoSQL). (founder/cto at YugaByte)

ralusek 7y ago
Joins and transactions across nodes, very cool. Inner joins/right joins too? Do these have similar time complexity, latency/bandwidth aside, as a comparably indexed traditional RDBMS?
- rkarthik007 7y ago
  Yes, we support all types of joins (inner, right included) and indexes. In fact, we recently also enabled stored procedures with plpgsql :) Tuning to perform these efficiently in a distributed manner is a work in progress (this is wrt the time complexity question). The hints used by a traditional RDBMS would not be effective in the distributed case - optimizing this requires changing the optimizer and doing more "push-downs" to optimize the queries. Currently, depending on the query, these may or may not be fully optimized - but we hope to have good coverage soon!