Hello,
I am working on a project requires
Presentation tier to have both Web Client and Smart Client. Web Client
(ASP.NET 2.0 Web Application) will be used by users globally through
Internet, and the Smart Client will be used in Intranet
administrators/Supporters (Expected concurrent users 20000).
At
this point, I am using WSSF (WCF) to build SOA to be consumed by Smart
Client. My question would be should Web Client call through the same
service interface built for Smart Client.
My main concern is following:
1.
If Web Application use the web service, would it affect the
performance I think the BasicHTTPBinding (WCF) will affect the Web
Application performance. How about NetNamedPipesBinding or
NetTcpBinding
Is Web Application calling through Web Service
recommended, if answer is no, please help suggest a architecture that
will meet the SOA at the same time meet the performance requirements.
Thank you in advance
SOA Web Application question
Hot Topic
- Windows Application Versus Web Site
- SPExport / SPImport problem with MOSS - help wanted!
- Error creating MySite: There has been an error creating the personal site
- Reports from Lists
- how to restore portal sites and contents from beta version? (MOSS 2007)
- Inheritance
- Good CMS open source.
- Deploying application hosted on a Web farm/SQL Server cluster
- Architecting Application?
- How to implement a Date class
SharePoint Products
- Modification Form
- Need a bit of help getting My Site functionality to work
- Architecture for Notification based application
- Start workflow when due date specified in list item has passed
- Feature Modeling with UML
- Server getting intimation of disconnection while file is downloaded from client side
- .NET data trasfer application architecture - windows service
- The participant 'HelloWorldParticipant' does not support action
- Samples for Profile Manager
- Question on Windows Forms App Best Practice
SOA Web Application question
Marleen
If you are building all of your processes so that they are accessible through WCF services, then you could just leverage your WCF services using NetTcpBinary, which is considerably faster than accessing an Asp.Net web service or using BasicHttpBinding. If you do not have any particular constraints that would force you to do otherwise (such as a public facing web service), then NetTcpBinary is the best way to go for performance.
Assuming that you are building these services so that they can be consumed by your own internal applications:
I'd suggest that you look into developing a WCF service layer that exposes all of your business processes, and then create, compile and deploy your own proxy libraries that can make the most effective use of your services. Your proxies can take care of service lookups, caching, logging, and other such functions for you while still using your WCF services for primary business activities.
-Graham