Re: partioning question
Cloud...
You will have to write code in a layer in front of the cloud.
Each cloud machine could have MySQL running.
Think twice about taking that job. Here are some of the non-trivial issues you will face:
* Data loss -- a cloud has lots of moving parts; the more parts, the more things that can fail. How will you replicate (or otherwise protect) the data from loss? When you start, data loss can be ignored. But when you tackle it, you will find that you need triple the machine and triple the software.
* JOINs -- VERY tough problem when a table is spread across multiple machines.
* Key-value -- easy to implement in a cloud. But that is the ONLY schema that is easy.
* How to find a piece of data? Hash? Dictionary lookup? Some combination (my preference)
* How to migrate data? You will eventually need this as a piece of the cloud gets full, or you add hardware, or etc.
* FEDERATED will take care of some of the above, but performance will NOT be to anyone's liking. PARTITIONing does not apply.
* You may be better off hooking up with one of the cloud services out there.
Subject
Views
Written By
Posted
4809
May 23, 2009 05:56AM
2989
May 24, 2009 09:29AM
3055
May 27, 2009 03:17AM
2850
May 27, 2009 09:50AM
2788
May 28, 2009 05:53AM
2407
May 29, 2009 12:36AM
2899
May 29, 2009 08:39AM
2820
May 29, 2009 10:49AM
2756
May 31, 2009 08:10AM
2838
May 31, 2009 12:11PM
2914
June 03, 2009 04:16AM
Re: partioning question
2856
June 03, 2009 11:20PM
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.