System Architecture / .NET Remoting

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm working on creating a SOA for my applications. We have
numerous .NET IIS applicaitons. They all tie into a central client
database for certain pieces of information. I'm trying to decide the
best way to architect the system.

Placing the business logic into stored procedures seems like an easy
way to allow all the different applications to access the business
logic there.

I'd prefer to somehow keep my Business logic in its own C# busines
layer. My concern is how each of my application will be able to share
that business layer. Would creating a .NET Remoting services be my
best option, or create a strict api and distribute it as a dll to each
of the applications be my best option?

Look forward to some insight....

Thanks

Sam

.

Relevant Pages