Comments on: SOA Anti-Patterns When Building Services

By: Benefits of Decoupled Service Contracts « Art of Software Reuse

Benefits of Decoupled Service Contracts « Art of Software Reuse — Sun, 13 Mar 2011 09:35:03 +0000

[...] contract tends to get expressed using the underlying technology platform – one of the many anti-patterns to avoid. This inhibits interoperability and increases integration effort for service consumers. [...]

By: william

william — Sun, 04 Oct 2009 19:25:02 +0000

Well in fact both. We separated Technical from Business services first. Then inside each type we defined more “domains”

By: SOA Patterns and Practices « Art of Software Reuse

SOA Patterns and Practices « Art of Software Reuse — Sun, 04 Oct 2009 15:48:35 +0000

[...] Patterns and Practices In an earlier post I listed a set of anti-patterns when pursuing service orientation within the context of building reusable software service [...]

By: Column 2 : links for 2009-10-01

Column 2 : links for 2009-10-01 — Thu, 01 Oct 2009 17:02:06 +0000

[...] SOA Anti-Patterns When Building Services « Art of Software Reuse Key anti-patterns include having only a project focus, and ad hoc reuse (which I suspect would be highly correlated). Good list of things to watch out for when building services. (tags: soa) Posted by Sandy Kemsley on Thursday, October 1, 2009, at 1:01 pm. Filed under BPM. Follow any responses to this post with its comments RSS feed. You can post a comment or trackback from your blog. [...]

By: Twitter Trackbacks for SOA Anti-Patterns When Building Services « Art of Software Reuse [artofsoftwarereuse.com] on Topsy.com

Thu, 01 Oct 2009 16:58:01 +0000

[...] SOA Anti-Patterns When Building Services « Art of Software Reuse artofsoftwarereuse.com/2009/09/30/soa-anti-patterns-when-building-services – view page – cached When building services and service capabilities for your enterprise you have ensure that you have right set of practices to succeed as a service provider. Here are a set of anti-patterns to avoid… (Read more)When building services and service capabilities for your enterprise you have ensure that you have right set of practices to succeed as a service provider. Here are a set of anti-patterns to avoid building enterprise service capabilities as part of your SOA initatives. You can use this as a list of things to watch out for and possibly course correct when/if you recognize them in your teams. (Read less) — From the page [...]

By: vijaynarayanan

vijaynarayanan — Thu, 01 Oct 2009 15:40:22 +0000

Agree William.

When you say categorizing services, do you mean categories in the company’s problem domain? or broad service categories such as entity services, task services, utility services etc.?

By: william

william — Thu, 01 Oct 2009 09:02:47 +0000

Not defining SLA – It is important to know how much request can be handle by the service. It also helps capacity planning

Not categorizing services: each service should fit in a service catalogue that is built incrementally and following a common taxonomy.

Not defining standards for XML schema, WSDl, WADL, JMS, URI naming, etc. It is important that all services follow some common technical standards.