SOA: Time For a Rethink
We need loosely-coupled services, not orchestration.
… the key really is to “Test fast, fail fast, adjust fast.”
— Michael Nygard
Wide Awake Developers: SOA: Time For a Rethink
« Atwood and Apple | Main | A Design Problem ... »
May 18, 2008
TrackBack
TrackBack URL for this entry:
http://www.typepad.com/t/trackback/18301/29211458
Listed below are links to weblogs that reference SOA: Time For a Rethink:
Comments
constructive nonconformist
Capsule
- A Single Point of Correctness
- Avoid Order Dependencies between Object Methods
- Disallowing Copying in a C++ Class
- Encapsulating a Thread in a C++ Object
- Get Off The Critical Path
- Hypertext and Application Workflow (or The Case for Single Node Apps)
- JavaScript Closures
- Know What You Know And Know What You Don’t Know
- RAII in C++
- The Back Button is Not an Undo Button
- Theory P: Software Development is Probabilistic
- Using Properties and Tuples to Get Multiple Values from a JavaScript Function
Recent Posts
Categories
Useful Links
Useful Books
Effective C++ CD
Scott MeyersEffective STL
Scott MeyersHead First Design Patterns
Eric Freeman, Elisabeth Freeman, Kathy Sierra, Bert BatesThe C Programming Language
Brian W. Kernighan, Dennis M. RitchieThe C++ Programming Language
Bjarne StroustrupThe Practice of Programming
Brian W. Kernighan, Rob PikeThe Pragmatic Programmer
Andrew Hunt, David Thomas
*
- Basecamp
- Backpack
- Technorati
Creative Commons
This workis licensed under a Creative Commons Attribution-Noncommercial 3.0 United States License.
This was the key take-away from a recent project post-mortem we did.
Build a small slice of something, end-to-end, and then test that.
You'll find problems a lot sooner than if you build out each layer in its entirety and *then* try to integrate them.
And earlier discovery means easier fixing.
Obvious in hindsight, I know.
Posted by: josephgrossberg | May 19, 2008 at 03:44 PM