Scaling web aps

May 4, 2006 on 5:53 pm | In php, mysql, webdev | No Comments

FuzzyBlog » Blog Archive » The Promised php|tek Podcast – Scaling Ookles

Great podcast, as expected!

A few questions/comments for Scott (included as comments on Scott’s blog)

1. ORM. The reason I liked ORM was that I could avoid the slurry of SQL statements everywhere. I guess you do have some sort of a database abstraction in the framework, which does not follow the ORM paradigm. Would love to have more details of it if possible.

2. You have mentioned Brad’s memcached in an earlier podcast. maybe it was me, but I think you did not touch on it in this one. Was it just an oversight, or is it something that you have not embedded in your framework? I was hoping you had, cause the danga.com site barely mentions php and memcache in one sentence!

3. While on Brad and livejournal, the link to his presentations is http://danga.com/words/2005_mysqlcon/mysql-slides-2005.pdf.

4. Single Databases. You mention this as a reason for staying away from ruby on rails and django. Are you saying that you have incorporated multi database support within OWF ?  Will appreciate details

5. Replication Hell. I agree that an Alter table statement can really cause havoc with replication. But what I fail to understand is why would you have an alter table statement on a production system? Maybe some maintenance needs might require you to add an index or two, but do u need to base your design on such a infrequest need? I find it difficult to imagine a production system , where table structures are changed on the fly.

6. What is your opinion on the Mysql 5 centric features like stored procedures, triggers and views? Have you used any, and if so, can you share your expereiences? I personally come from a sybase background, and have used atleast the first two a lot. Unfortunately my shared host just has mysql 4, so have not been able to test these out on my own.

 

  

technorati tags: mysql, scaling