Views
- State: published
The Everything Loosely Coupled Architecture
Document Actions
|
|
Jon Udell writes about Adam Bosworth painting the big picture. Adam tells about some first principles for the future of applications:
Coarse-grained messaging. Get everything you need in a single round trip.
Public contracts. You can change your operating system, you can change your object model, but don't change your public contract.
Asynchrony. "I've been surprised by how slow some companies have been to pick up on asynchrony."
Message-driven model. We need a programming model for message-driven programming.
Declarative query. "We don't have a good query mechanism for XML."
Scripting. "dynamic runtime-modifiable systems, rather than static compile-time systems that make you shut down and restart your services."XML repository. It sees a lot of self-describing XML messages, and it has to do high-performance storage and retrieval.
Well surprise, almost identical to what I enumerated in my Loose Coupling blog last November. However, though its nice to enumerate hodgepodge of characteristics, how does this kind of architecture look like? Also, what kind of new software constructs do we need to manage this kind of architecture?
Note to self: Derive A Everything Loosely Coupled Architecture.
Last modified 2003-07-30 04:15 PM
