The Web Way

Interesting quote from this post:

The Web Way is a philosophy toward Web-based services:

1. They should be as simple as possible, but no simpler.
2. They should have clean designs for user interfaces and clean designs for programming interfaces.
3. Where it's useful, they should embrace REST.
4. Where it's useful, they should embrace loose coupling.
5. Where it's useful, they should embrace glorious, nonblocking, asynchronous pubsub. ;)
6. Where it's useful, they should embrace microformats, a/k/a lowercase semantic web.
7. Where it's needed, they should embrace the time-tested principles of Scalable Internet Architectures (three simple rules: optimize where it counts, complexity has its costs, and use the right tool).

We are moving in that direction :). I have been thinking about REST, continuation, Cornerstone Action, caching, session and forward propagation model / dependency caching all together these days and realized we may have the best practice of taking all of them into account and implementing a scalable, easy to develop and evolve system architecture.