Well certainly there are some very large sites using Cold Fusion every
day... and the list is growing daily.
I've yet to find a solution where the actual application or database design
was not the cause of the failure to scale. Many designs work well for one
server and might work well on two or three, but after you put lots of
different different applications under high load in the same environment,
you'll likely find that you need to do tuning. The consumer code does one
thing, infrastructure code another, backup processes lock some items, etc.
The way to scale is to design your application with scalability in mind.
Will caching help? How much can you cache? Can you offload static content
to non-CF servers or distribute that content around the Internet for faster
access? How often do you really need to hit a database? How much code is
transactional and how much is "lookup only (read only)"? If it's read-only
can you build a read-only server? The tips and tricks are endless. CF, ASP
and others all scale, but only when the environment and applications are
designed to do so. In my opinion it's far easier to write with CF and build
the applications quickly and I prefer it immensely. However, due to its
simplicity, it's also too easy to write things "quickly" and in so doing not
take into account what is required to scale. In the Web's urgency to get to
market, scalability and stability are often overlooked.
That's my two cents.
--Doug
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
