I'm in the middle of learn and apply CSLA.NET 4 for my project. First I'm sorry if my english is not too good.
I haven't known about SOA and implementation in microsoft technology.
Currently i have a situation :
There is a medium company that separate on several location,
1 Head office and several branch office, and then there is a requirement that a branch office can does a "posting activity" ( their term ) which is save sale transaction into head office ( after that branch office can't edit that transaction until head office do next act on that transaction ). Next, head office can does a similar action on sale transaction so that those transaction will be synchronize into branch office again.
My Questions :
1. Is SOA is suitable for this scenario ?
2. I interested with Roc explanation on book 1 overview, but I don't have clear knowledge about develop CSLA.NET + SOA for this scenario if applicable ?
3. This is my personal requirement : If i want to make a synchornization from Head Office to Branch Office or otherwise, but i don't want user to reload reload and again to know if there is already changing from remote office, instead I want on the Branch office screen the changing on Head office will arise as soon as the head office user does that changing WITHOUT RELOAD on branch office screen ??
Thanks a lot all
In order to achieve #3 you will need an architecture where you:
1. Use WCF Services with WsDualBinding so that you can send notifications to clients on changing data.
2. This limits your use of CSLA 4 to be an Edge application, ie: you will most likely only use CSLA for the client application.
Hi jonny thanks for your quick response
I will try to research and learn about WCF.
But could you explain more about point number 2, like a suggestion architecture for collaboration CSLA.NET as an edge app and WCF as a webservice ??
thanks a lot
What Jonny is saying, is that in a service-oriented system, you have 2 or more applications that interact with each other via loosely coupled, contractual messages.
To say that another way: if you don't have 2 or more applications interacting via messages, you aren't doing SOA.
You might be using service-based technologies (like WCF or REST), but just using a service-based technology doesn't mean you are following any specific architecture.
So if you wanted to build your solution using SOA, you'd be created a service-oriented system composed of 2 or more applications, and those applications would interact via loosely coupled messages. In your case, that would imply that you have a server application with a service interface, and a separate client application that interacts with the user through a GUI. These two, completely separate, applications would interact with each other via contractual messages.
The client applications in a service-oriented system are often referred to as "edge applications" because they sit on the edge of the system, and allow users to interact with the system in useful ways.
Hi roc thanks for your response
and I'm sorry for my PM to you about MVVM video series before.
What you said above is it same like your overview ebook ??
My mean : 2 or more app i build with CSLA where each app server or edge, i use 5 logical layer with
server has interface a server / WCF contract message and client has a UI to communicate with WCF contract message ( server ) ??
where each app ( 5 layer ) use CSLA as a business logic layer ??
thanks a lot
Copyright (c) Marimer LLC