- David asserts very clearly that “it’s essential to avoid coding business logic into the client layer“.
Why? What’s wrong with coding some business logic into the client layer?
- What is wrong is, imho, trying to defeat the principles of physics by mixing and shortcutting layers in a multi-layer architecture.
- What is wrong also is mixing the business logic and the presentation
But this does not have much to do with coding business logic in the client.
A statement like the one of David sounds, to me, one of the myths that populate our IT culture (such as “open source is great” or “Linux is better than Windows”)
I have sent David a mail asking him to read my comments titled Composite Applications, Mashups and Portals: “relay race” or “team spirit” ? and Two faces of the same coin.
I hope this could be useful for triggering some more discussion.
I do not agree with everything John wrote…. but I certainly agree when he makes a distinction between free-services and business-oriented services, for which a contract is required!
Update from February 22.
I have just read an interesting article from David Linthicum: Enterprise mashups meet SOA. I want to quote a couple of interesting sentences:
- Mashups and SOA are part of the same continuum. By linking the new components of Web 2.0 with our own sets of information and services, mashups provide a quick and easy way to solve many of today’s simple business problems — and should scale nicely to solve more complex and far-reaching problems in the future. They make the value of an SOA much more visible over a much shorter term.
- An enterprise that can’t see the new Web will have a huge strategic disadvantage in the years to come.