Re: Multiple Table-Model, Multiple DB
Jeremy Burns, I truly salute you for such a detailed explanation. Actually, I always prefer RDBMS. I just wanted to try a new concept. I have already mentioned that this is just a concept, nothing into implementation. We are just brainstorming. Our boss likes any new idea, let it be bullshit. He later decides what suits the best. I personally think sometimes it's better to make mistakes and learn. My concept I talked about, actually came from another project that I'm maintaining right now. The project was build few months ago by someone else, and it has few thousands of members now. Gradually as the members grew, their data about their activities grew exponentially. Now the activities tables has few millions of rows. Initially the site was giving very good performance, but now, its super slow. Our team found out that mysql is the bottleneck. Now we have decided to build our projects in-house rather than outsourcing. So we're just brainstorming what could be a good solution for us. I know we can use RDBMS with MySQL Cluster, or even NoSQL with MongoDB or many other solutions are out there. Initially, I just thought this will be a cheap option to go with. Later on, I just understood my mistake. Thank you very much for your time. NB - Please forgive my poor english, as i'm not a native english speaker. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups CakePHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en To unsubscribe, reply using remove me as the subject.
Multiple Table-Model, Multiple DB
I am newbie in CakePHP, using it only for 2 days. I am using PHP 5.2.10, MySQL 5.0.84, CakePHP 1.2.6. I have two questions. Scenario 1. While designing my site in paper, I decided to split my tables into parts ( For example, member table will be like member_us_ny, member_us_ca, member_intl_en, member_intl_fr, etc.) to make it easier for MySQL manipulate member info. I know MySQL is able to handle millions of rows, but still I think handling 10 thousands rows is better than handling 1 million rows. This is just a concept. I can get the user location as soon as they are accessing my site. Ques 1. Can I implement tables like this in CakePHP within a single db model? Scenario 2. I want to avoid relational db concept and implement my site with structural concept, so that I can implement parts of DB in different servers. For example, members in one server, products in another, access_info download_info in another server, and so on. I know there are different options to implement this without using MysQL. I want to do this because, I am trying to avoid MySQL Cluster or MongoDB or MemcachedDB or anything like that. I want MySQL to do the job. Ques 2. Will I be able to use multiple DB in CakePHP? Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups CakePHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en To unsubscribe from this group, send email to cake-php+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
