SOA - Modularity, Delegation, and Federation

What are the core features that bring power to an SOA? I think they really come down to three things: modularity, delegation, and federation.

• Modularity is the componentization of software into discreet functional unit (the real key here is standardization within the modularity)
• Delegation is the ability to act as a delegate to perform a unit of work for another process
• Federation is the ability to provide a network of delegates that are independently maintained and operated.

I’ll get into a lot of this stuff in more detail in future entries, because each of these really has some interesting nuances, but I think that there are two really interesting things about these three items.

1) These three things are completely independent of the underlying technology, and;

2) You can have an SOA that doesn’t do a very good job at one or two of these, and you’ll never really get the full benefit of SOA

SOA Anatomy

Having worked as Technical/Enterprise Architect for a while, I thought about writing my views on an Agile SOA based architecture. I am starting with a rough sketch of a generic architecture, which I'll keep on detailing as I continue to fill my blog space. I plan to create 3 generic architectures for J2EE, .NET and OpenSource product families. So here is my first stab at it.

Diseased with religion?

Religion is like a disease of the human mind. It's like rabies. You get bitten and suddenly there's this great foaming at the mouth, all senses and reason thrown to the wind. There's a lot of shouting and then you bite someone else in all the madness and it gets passed down the line across generations, and national boundaries. Forget AIDS. This stuff kills millions.

Work Haiku V 1.0

All day I sit here

Pretending to work real hard

While I write haikus