Thoughts on RIA Services and Multiple Domain Services
Michael D. Brown
If anyone’s interested, there was a thread in the RIA Services forum about using multiple domain services. I’ve recanted my earlier position that there should only be one Domain Service per app. Check it out here. I’m wrapping up the first draft of my article for the publisher now. If anyone wants to review for technical accuracy (looking at you Colin) I’d be much obliged.
Sincerely,
Michael D. Brown MVP Client App Development President p: 312-725-XAML |
|
CBl...@eki-consulting.com
Send it, I will take a look.
Having multiple DomainServices is primarily bounded by two technical limitations. The first limitation is that you can't have two DomainServices returning the same type of entity. The second limitation is that Silverlight does not have any support for distributed transactions so you can't have a change made to two different DomainServices (or two instances of the same DomainService for that matter) and be able to roll back.
The first limitation is specific to RIA Services and can be fixed by the RIA Services team whenever they want to. The second limitation is a general Silverlight limitation and can only be fixed in a new version of Silverlight.
"Michael D. Brown" <mike....@azurecoding.net>
Sent by: wpf-di...@googlegroups.com
03/14/2010 05:34 PM ASTPlease respond towpf-d...@googlegroups.com
To <wpf-di...@googlegroups.com>
cc
bcc
Subject [WPF Disciples] Thoughts on RIA Services and Multiple Domain Services
| MVPLogo.gif |
Michael D. Brown
The idea of the bounded context is that operations occur only within one context. Basically you could think of it as subsystems within a larger application. As such, there is no need for transactions to cross contexts. Also the entity duplication is unfortunate but also not a major issue seeing that technically the entity belongs to a separate namespace in different contexts (and will have different logic associated with it). I don’t have any discussion about this pattern in the current revision of my article. At this point, I’m considering expanding on my article and following Josh’s footsteps to turn the topic into a book. Of course I have to get the article done first right ;)
Sacha Barber
Sacha Barber
sacha....@gmail.com
Corrado Cavalli
The idea of a book/ebook sounds great, about your MSDN article,
I'd like to have a look at it, are you going to spend some words
on deploy too? I see many people having trouble with that.
Cheers,
Corrado
On Mon Mar 15 03:36:58 CDT 2010, Sacha Barber
<sacha....@gmail.com> wrote:
> Watch out with that book idea, and make sure to run it by Justin
> first eh
> :-)
>
> On Mon, Mar 15, 2010 at 1:38 AM, Michael D. Brown <
> mike....@azurecoding.net> wrote:
>
>> The idea of the bounded context is that operations occur only
>> within one
>> context. Basically you could think of it as subsystems within a
>> larger
>> application. As such, there is no need for transactions to cross
>> contexts.
>> Also the entity duplication is unfortunate but also not a major
>> issue seeing
>> that technically the entity belongs to a separate namespace in
>> different
>> contexts (and will have different logic associated with it). I
>> don?t have
>> any discussion about this pattern in the current revision of my
>> article. At
>> this point, I?m considering expanding on my article and
>> following Josh?s
>> footsteps to turn the topic into a book. Of course I have to get
>> the article
>> done first right ;)
>>
>>
>>
>> *From:* wpf-di...@googlegroups.com [mailto:
>> wpf-di...@googlegroups.com] *On Behalf Of
>> *CBl...@EKI-CONSULTING.COM
>> *Sent:* Sunday, March 14, 2010 7:58 PM
>>
>> *To:* wpf-di...@googlegroups.com
>> *Subject:* Re: [WPF Disciples] Thoughts on RIA Services and
>> Multiple
>> Domain Services
>>
>>
>>
>> Send it, I will take a look.
>>
>> Having multiple DomainServices is primarily bounded by two
>> technical
>> limitations. The first limitation is that you can't have two
>> DomainServices
>> returning the same type of entity. The second limitation is that
>> Silverlight
>> does not have any support for distributed transactions so you
>> can't have a
>> change made to two different DomainServices (or two instances of
>> the same
>> DomainService for that matter) and be able to roll back.
>>
>> The first limitation is specific to RIA Services and can be
>> fixed by the
>> RIA Services team whenever they want to. The second limitation
>> is a general
>> Silverlight limitation and can only be fixed in a new version of
>> Silverlight.
>>
>>
>> *"Michael D. Brown" <mike....@azurecoding.net>*
>> Sent by: wpf-di...@googlegroups.com
>> 03/14/2010 05:34 PM ASTPlease respond
>> towpf-d...@googlegroups.com
>>
>> To <wpf-di...@googlegroups.com>
>> cc
>> bcc
>> Subject [WPF Disciples] Thoughts on RIA Services and Multiple
>> Domain
>> Services
>>
>>
>> If anyone?s interested, there was a thread in the RIA Services
>> forum about
>> using multiple domain services. I?ve recanted my earlier
>> position that there
>> should only be one Domain Service per app. Check it out
>> *here<http://forums.silverlight.net/forums/p/83198/378018.aspx#378018>
>> *. I?m wrapping up the first draft of my article for the
>> publisher now. If
>> anyone wants to review for technical accuracy (looking at you
>> Colin) I?d be
>> much obliged.
>>
>>
>>
>> Sincerely,
>>
>>
>> Michael D. Brown
>>
>> MVP Client App Development
>>
>> President
>>
>> *KharaSoft, Inc. <http://kharasoft.com/>*
>>
>> p: 312-725-XAML
>>
>> *MVPLogo.gif
>> <https://mvp.support.microsoft.com/profile/Mike.Brown>*
>>
>>
>>
>
>
>
> -- Sacha Barber
> sacha....@gmail.com
>