Thin Client VB.NET Application - 3 tier architecture

Posted on 2009-02-17
Last Modified: 2013-12-17
Dear Experts,

I need to develop a thin client application in VB.NET.
This is what I mean by thin client - I need to provide a user interface ( probably developed in VB.NET) for our users. With this, I want to separate all the processing/logic and the database related access so that this all happens at our server and the user interface is thin.

I am not sure how to go about this implementation and deployment of these kind of applications.
Should I develop application with three tier architecture in VB.Net? If so how can I provide just the UI to the users and retain the database layer and the business layer at our server

Any sample examples or website links will be of great help.

Thank You in advance
Question by:arsmed840
    LVL 1

    Expert Comment

    To create the three tier architecture you would want to of course have the database tier, then create a web service for the business layer, and third a web site for the user interface.

    If your not sure how to create or call a web service this video should give you a basic understanding.
    LVL 24

    Accepted Solution

    Web services aren't the only option for the business layer. In fact, if you're planning on controlling both ends of the pipe, I'd strongly recommend using a WCF service with net.tcp bindings for performance reasons.

    It also depends on your choice of UI technology. A web application is about as thin as you can get, but these have some issues -- like needing validation logic on the client side, and generally having to write that in javascript, while your server-side validation is in .NET. Silverlight eases this pain a little bit, but introduces a whole bunch of other issues.

    However, if you require a great-looking UI, you're likely looking at Silverlight, WCF or an ASP.NET pages. WinForms are so last decade.

    You're going to end up with two (or more) deployment packages -- one for the client and one (or more) for the various server-side pieces.

    When architecting your services, be sure that you use chunky interfaces. One of the worst things you can do for performance and scalability is have frequent, small calls to your services. You want a coarse-grained API exposed to the client, so that significant tasks are performed with a single service call.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Find Ransomware Secrets With All-Source Analysis

    Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

    I use more than 1 computer in my office for various reasons. Multiple keyboards and mice take up more than just extra space, they make working a little more complicated. Using one mouse and keyboard for all of my computers makes life easier. This co…
    Skype is a P2P (Peer to Peer) instant messaging and VOIP (Voice over IP) service – as well as a whole lot more.
    The viewer will learn common shortcuts with easy ways to remember them. The viewer will then learn where to find all of the keyboard shortcuts, how to create/change them, and how to speed up their workflow.
    An overview on how to enroll an hourly employee into the employee database and how to give them access into the clock in terminal.

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    13 Experts available now in Live!

    Get 1:1 Help Now