What is the best architectural solution for the combination of InnoDB and NDB tables
(A) We have a database in development with over 100 tables. 80% of them are small and are InnoDB candidates. The rest are NDB candidates.
(B) In production we plan to have 3 separate databases. One each for USA, India and China.
(C) We intend directing customers by country to their respective databases.
(D) We plan to have a cluster implementation with 6 data nodes over 3 node groups for each country.
So the questions that I have are:
1. What is the best architectural solution for the combination of InnoDB and NDB tables.
2. Will MySQL Proxy be useful for re-direction?
2. Is it possible to have a "list" sub-partition under hash KEY partition (for the NDB) tables.
A quick reply will be highly appreciated.
Regards,
Prithwi
Edited 1 time(s). Last edit at 12/04/2007 04:54PM by Edwin DeSouza.
Subject
Views
Written By
Posted
What is the best architectural solution for the combination of InnoDB and NDB tables
3454
December 04, 2007 02:07PM
2548
December 04, 2007 04:59PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.