On 19 nov, 23:41, jacmoe <[email protected]> wrote: > To me, a 'larger project' is simply a project with a lot of code. :P
By that measure, a lot of truly awfully code constitute "large projects". [1] > It has less to do with how many users it has/gets. I disagree. You don't hit scalability, caching, concurrent, bottleneck problems on a 'big' app which never has more than a few active users at a time. I think this: http://micropipes.com/blog/2008/04/23/caching-is-easy-expiration-is-hard/ is a perfect example of a problem that simply doesn't exist until you have a bigger app. Large project for me means at least being big enough to truely require numerous dedicated servers (and e.g. a cdn). in traffic, that depends on what the app does. if it's very interactive that could be only a few 10K users. AD [1] http://twitter.com/jperras/status/5846555120 live it -- You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cake-php?hl=.
