I guess the trick is to make sure your servers are close to the database... like running on force.com ;-) I guess for most sites, users won't really notice a f

I guess the trick is to make sure your servers are close to the database... like running on force.com ;-) I guess for most sites, users won't really notice a few hundred milliseconds. I mean, most websites take many seconds to load when you factor in all the individual files and images, etc. UX performance is more about perceived delay (by end-users, not us technical folk) rather than actual delay. If you want to use a product like this so you no longer have to think about your database (and are willing to pay what seem to be quite high fees), design your application to account for the fact that there will be large amounts of lag... that's what parallelisation and non-blocking IO is for.