Facing and Indexes

I want to outline my database, but I am not a professional in this topic. So, here are my thoughts. Although the key key is a great index for directing queries to the right nodes, what about the rest of the indexes that will be defined on my tables? I want queries that reference these indexes to be delivered to the correct nodes, so that only one node processes the request. As I understand it, there must be some centralized index nodes. So my question is whether this functionality is present in the DBMS like MYSQL or should I use other special products.

+5
source share
2 answers

Disclaimer: I work for ScaleBase , I live and suffocate every day ...

I would advise here that if you outline, for example, in column A, then WHERE with columnA = xx will go to one shrad. WHERE columnB = xx must go through all the fragments, because in all of them there may be a column B = xx. If columns A and columnB are not specified. And then you really need to keep the relation in the mapping table. I can say that work on all databases can be super-fast, you need to run in parallel and combine the results. In ScaleBase, we support combining ORDER BY, GROUP BY, etc. It's not easy...

Hey, see more details on your blog: http://database-scalability.blogspot.com

0
source

, , , Clustrix, , . Clustrix " " ( ). MySQL , , , , .

0

All Articles