Re: System Architecture / .NET Remoting

Peter:

I guess my question is what is the best way to expose the applicaiton
server.

Currently, our applications are very tightly coupled with lots of
duplicate code. The majority of our business logic is contained in
SQL stored procedures. I'm looking to refactor the system. I guess
I'm looking for more information how people commonly "encapsulate all
our business logic in remote components running on an
application server" Also, I was trying to determine if the best way
to connect our webservers or any other clients to the application
server is though the .NET Remoting Framework. This is all new to
me....

Thank you for the help!

Sam


On May 4, 9:15 am, "Peter Bradley" <pbrad...@xxxxxxxxxx> wrote:
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" <sshref...@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- Hide quoted text -

- Show quoted text -


.

Relevant Pages

  • Creating/Altering Database Schemas via Code
    ... to create/alter the database for a suite of ... the server in an INI file) ... I have never heard of major applications (a suite of at least 9 client ...
    (microsoft.public.vstudio.general)
  • Limiting applications database size
    ... I have a database server that contains several applications. ... to facilitate one-on-one interaction with one of our expert instructors. ...
    (Security-Basics)
  • Re: Access Control Best Practices for shared hosting seem at odds with Web Site Starters
    ... the full context of the bullet I quoted appears to be the HTTP POST ... Do not allow anonymous user to have write permission. ... content to the server, then they can write anything onto the server. ... More secure alternatives are applications that store ...
    (microsoft.public.inetserver.iis.security)
  • Re: Data source options
    ... This is pretty much how FlashConnect was designed to operate. ... FlashConnect executable, referenced in the URL, resides on the web server ... > browser-based database application where the backing database is not ... > If you look at various rich internet applications, ...
    (comp.databases.pick)
  • Software Developer Lead for New Mobile Device Product
    ... with a client in Austin who has the following opening. ... is in need of a Passionate Software Developer who is hands-on to lead ... commercial work experience in both web and server side applications. ...
    (comp.lang.java.programmer)