Comments on: Aggregated Web Services Pt I

By: Tying it Together « Composite Code

Tying it Together « Composite Code — Fri, 03 Sep 2010 21:41:42 +0000

[...] of an assembly/classes between multiple web services projects. I wrote about it initially in Aggregated Web Services Pt I. In this blog entry is going to cover a few things, based on a full end-to-end implementation of [...]

By: DotNetShoutout

DotNetShoutout — Thu, 29 Jul 2010 15:38:48 +0000

Aggregated Web Services Pt I « Composite Code…

Thank you for submitting this cool story – Trackback from DotNetShoutout…

By: Adron

Adron — Wed, 28 Jul 2010 16:00:37 +0000

I’m digging Lynn’s material, thanks for the link Marty.

By: Marty Nelson

Marty Nelson — Wed, 28 Jul 2010 15:28:29 +0000

It’s hard to evaluate without some notion of the overall size of the data, it’s rate of change, complexity of allowable query, typical size of the data response, etc.

From your diagram, I gather you want to maintain a complete set of aggregated data in your cache. If this is the case, why not decouple it completely from the application (it’s just “the data repository”) and have the replication mechanism be completely separate.

You might want to check out this video from lynn langit were he talks about async willing of queue from multiple sources to fulfill a request: http://www.slideshare.net/lynnlangit/windows-azure-platform-2626957

By: Adron

Adron — Wed, 28 Jul 2010 15:01:37 +0000

I’m actually concerned about this too (the complexity), as it has the dreaded redundant architectural pieces. I’ll elaborate more in Pt II that I have coming and layout some of the code I’m putting down for it. Also to note, this is actually a real world scenario, that will most likely be going to production in about 5 months. So we will definitely see if it holds water – this boat could still sink and I have to do a complete redesign. Thanks for the comment Kirk! I look forward to additional feedback as I post more! -Adron

By: kirk

kirk — Wed, 28 Jul 2010 14:13:47 +0000

Great job, Adron.

My only comment after looking at your architecture (with the intent to poke holes) is to question the complexity for a read-only site. As a lover of technology and someone w/ keen interest in all of the different aspects of your architecture, the complexity is interesting, but I would question whether, in a real-world scenario, with time constraints, budgets, are you decreasing the chances of success. Food for thought. I’ll keep reading along.