Distributed Design Question -- dotnet distributed apps

billr
8/5/2005 6:42:04 AM

Sounds good to me.

And if you want to lock down access to your webservices, you can implement a
SoapHeaderExtension to contain security information, this way when the web
service receives a request you can discard the entire request if the header
is not present.

So, in your DMZ (where your external users will come from) you simply check
the security credentials and allow/deny further access. If access is granted
then the request is simply passed onto the business layer (accessed via web
services) which resides behind your firewall. Clients working from behind the
firewall simply connect directly to the business layer.

--

--

Of all words of tongue and pen, the saddest are: "It might have been"

[quoted text, click to view]

Max A. Bündchen
8/5/2005 9:09:29 AM

Hi all,

I have a new project for a long time software like a ERP. This system will
work around a organization but must be accessible from the internet (for
vendors, travelers and so on). I think that we have around 200 clients in
the intranet and more 50 in the internet.

The design that I have select is a smart client application with webservices
in the middle running the logic of the program in the server.

I have many applications with webservices, but not as the middle software.

What about this line of application?

Max A. Bündchen
8/9/2005 5:02:46 PM

I think it's a good solution, of course. My fear is about performance. The
webservice is very slower than other solutions like a Remote by TCP or
Enterprise Services. For other hand, if I implement a solution based on
Enterprise Services or Remote, I need to implement a extra layer with
webservices just for clients from internet.

Anyone have tested the performance of a solution like that and the
scalability of this same solution.

Thanks,

Max
[quoted text, click to view]

billr
8/15/2005 3:43:03 AM

Max,

the approach I outlined in my previous post is exactly the approach we
decided upon for a Multi-million pound (sterling) generating application (no,
unfortunately, it doesn't make money!), it is a fully distributed system
using a dotNet smartclient for the front end, connected to a DMZ webservice
layer, which in turn is connected to the firewalled application server
cluster.

Web services themselves should be small and fast, and business logic should
be moved outside of your webservices.

--
--

Of all words of tongue and pen, the saddest are: "It might have been"

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet distributed apps

dotnet distributed apps : Distributed Design Question