Shadowfax: getting my hands dirty with a SOA-like architecture
Note: this entry has moved.
Recently, I started working with
Shadowfax, a reference architecure coming from the
Patterns & Practices group at Microsoft. You have a look at an
overview of the architecture at the GDN workspace home. I also recommend
Hernan de Lahitte's blog, one of the guys working on it. He has a nice
introduction as as well as a
closer inspection of the processing pipeline.
I don't to repeat those intros. I'll just say that if you're developing SOA-like
architectures, or you need one for your project, you should definitely take a
look. It's being developed in a very open manner, with source releases pretty
often, with open feedback through the workspace, and even if it's not ready for
prime time yet, it's a good indication of where MS thinks you should be going
with your projects. It closely follows the advises from Application
Architecture for .NET: Designing Applications and Services, and
generally represents a pretty good compendium of best practices. It makes heavy
use of several application blocks from PAG, su as
Configuration Management Application Block,
Authorization and Profile Application Block an the
Logging Application Block.
As this is going to take most of my working day now, I'll start a new category
for these posts.
I hope ScottW adds support
for subscribing to a single category soon (as dasBlog
does since quite a while...). This way, you can subscribe to this single category if you want.
I have the task of helping developers have a smooth experience
when programming against Shadowfax. I'll drop my ideas here, as well as
the dev. aids I think could be useful. Even if you don't use Shadowfax, it
would be cool to get your feedback... because it's possible that some of my
ideas seem useful only to me! Stay tunned, lots of posts are coming ;)