[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [soa-blueprints] Anti-Blueprints
There are some SOA anti-patterns that will be common to general software but there will also be specifics to SOA (like don’t start with process). I’ve no idea who said it but I recall reading once a phrase something like “IT is 5% what to do, and 95% what not to do”. Having anti-patterns is at this stage almost more valuable than proper patterns as they act as breaks on development expense that would be pointless. I know of a few clients I’ve saved money for by pointing out what is wrong who are now taking the time to move towards a more controlled blueprints type approach.
Not only does IT need the “This Way” signs, we also need “There be dragons”.
From:
Matt MacKenzie [mailto:mattm@adobe.com]
Why is it valuable to define an “anti-pattern” such as the one discussed here? Doesn’t this anti pattern apply to pretty much all programming models? It looks like y’all are fishing here.
Just my CAD$0.02…
-matt
From:
Miko Matsumura [mailto:mmatsumura@infravio.com]
Good feedback Duane.
This is a good topic, thanks for introducing it, Steve.
The number of services *is* a quantitative measure, but perhaps not a very helpful one? =)
I'm pretty sure there's an antipattern here, and I think perhaps there could be some kind of way to assess this. I think another variable in this mix is the extent to which the registry repository in question can help with respect to discovery and classification as well as governance. The thing that worries me is when I see people assuming that fine grained (object level) services will be reused, when the reality is that OO didnt generate that much reuse from even the guy in the next cubicle, let alone across the company or across the planet.
I think this is less of a gross number of services antipattern so much as a coarse-grained vs fine-grained antipattern...
Best, Miko
From:
Duane Nickull [mailto:dnickull@adobe.com] I disagree with this anti-pattern.
I am not sure that the number of services is really a quantitative measure of SOA. A grid computing cluster administrator may be able to rationalize such behavior, although it may seem absurd in other areas such as Amazon deploying a service for each book it carries vs. deploying one service that allows the consumer to parameterize the book title.
Perhaps a better measure would be the development of some test criteria to ascertain whether a contemplated service is a good candidate for repurposing beyond a small number of consumers. This should be based on alignment with LOB and presumably different implementers will have different criteria for quantifying such.
Duane
From:
Miko Matsumura [mailto:mmatsumura@infravio.com]
I just added a "microservice" antipattern where programmers put 10000000 WSDLs into a registry just because their IDE lets them do so.
Miko
From:
marchadr@wellsfargo.com [mailto:marchadr@wellsfargo.com] Steve,
Good idea. I put up the first drafts of them at: http://blueprints.jot.com/WikiHome/SOA+Anti-Patterns/SOA%20Anti-Patterns
Let me know if I correctly eloborated and named them for you.
Thanks,
Dan
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]