Re: System Architecture / .NET Remoting

Not sure I've understood you correctly - but it seems to me that you should
have no problem sharing your SOA amongst many applications. As long as they
have a definition, client side, of the remote object's interface/metadata or
whatever, they can just make calls via the remoting framework. Have I
missed something in what you're trying to do?

We encapsulate all our business logic in remote components running on an
application server. All database access is done via the business logic
layer. This means that the Web server can be off the domain, and totally
ignorant of anything to do with database connections and the like. As far
as the Web server is concerned, we could be storing data in csv files. It
doesn't know and it doesn't care.


Peter


"Sam Shrefler" <sshrefler@xxxxxxxxx> wrote in message
news:1178283588.344353.204230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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

  • Re: Newbee on web apps with Delphi
    ... > I need to develop my first web application with delphi for database ... I'll try to describe what I know about writing such applications: ... session (but I gave up on this as the Apache Web server couldn't handle it). ... ASP.NET (Delphi 8->): I've just started looking into this one, ...
    (comp.lang.pascal.delphi.misc)
  • Re: polymorphism (was: Poly Couples)
    ... but this is not really "business software"... ... Most of such applications are built as a combination of ... database with flat files or a different RDBMS vendor?" ... couldn't care less if I do it in using structured programming or OOP ...
    (comp.object)
  • Re: Unisys OS/2200 DMS / TIP / COBOL Migration
    ... support the legacy system api's that the application is using. ... differences in COBOL compiler dialects. ... What DBI does is to provide legacy database (DMS) ... the legacy database to the COBOL applications. ...
    (comp.sys.unisys)
  • Re: Database set up help
    ... let's see...I choose the y/n data type because I am using ... User opens up form and enters Employee Information in the fields ... 2 of the 38 options in my main menu are BPCS Applications ... I set up a database with this so far: ...
    (microsoft.public.access.gettingstarted)
  • Re: Advice needed for a growing Access 2000 project
    ... However, it turned out that quite a few of those were "leftovers" from previous releases, no longer accessible from anywhere but the database window, and, thus, no longer used. ... But that certainly isn't the _norm_ -- without any 'heroic' measures, there are routine reports of split Access DBs ... Finally, in my opinion, for "Windows apps", that is, individual-user applications, modest-sized multiuser applications, and client-server applications of any size, Dot Net does NOT "help along" any of these issues. ... The post I reference was in reference its self to the MS Access Help file under "Microsoft Access database general specifications" ...
    (comp.databases.ms-access)
Loading