The Anatomy of a LightSwitch Application Series Part 1 - Architecture Overview

The Anatomy of a LightSwitch Application Series Part 1 - Architecture Overview

Rate This
  • Comments 21

The announcement of Visual Studio LightSwitch this week has generated a lot of discussion, and as expected a number of questions about "what is LightSwitch really building under the covers?".  To help shed some light on that (sorry, couldn't resist) we're putting together a blog series that takes a more in depth look at the Anatomy of a LightSwitch application.  We'll start with this high-level architectural overview and then drill into each architectural layer and other specific topics over the coming weeks. 

Here's an outline of topics we're thinking about:

(UPDATE: In Visual Studio 2012 (LightSwitch v2) we have updated the middle-tier architecture to use OData Services. See: LightSwitch Architecture: OData)

(UPDATE: In Visual Studio 2012 Update 2 (LightSwitch v3) we have added an additional client option, HTML5. See The LightSwitch HTML Client: An Architectural Overview

With that, let's get started...

The Anatomy of a LightSwitch Application - Architecture Overview

Microsoft Visual Studio LightSwitch applications are built on a classic three-tier architecture. Each tier runs independently of the others and performs a specific role in the application. The presentation tier is responsible for human interaction with the application. Its primary concern is data visualization and editing. The logic tier processes requests from a client to fetch data, update data, or to perform other operations. This tier’s primary role is to shield direct access to the data from unwanted or invalid reads and updates. This helps to ensure the long-term integrity and security of the data. The data storage tier is responsible for durable storage of the application data.

A typical three-tier application

Designing a new three-tier application from scratch can be difficult and complex. Each tier presents a myriad of technology choices and internal system design. Each has distinct deployment and manageability concerns. Each must handle communications with the adjacent tier, and ensure secure access from trusted sources.

LightSwitch removes the complexity of building a three-tier application by making specific technology choices for you. You concentrate on the business logic and not the plumbing.

When we map the specific technologies used in LightSwitch to this architecture you find that the LightSwitch presentation tier is a Silverlight 4.0 application. It can run as a Windows desktop application or hosted in a browser. The LightSwitch logic tier exposes a set of WCF RIA DomainServices running in ASP.NET 4.0. The logic tier process can be hosted locally (on the end-user’s machine), on an IIS server, or in a Windows Azure WebRole. A LightSwitch application’s primary application storage uses SQL Server or SQL Azure and can consume data from existing SharePoint 2010 lists, databases accessible via an Entity Framework provider, and custom build WCF RIA DomainServices.

A LightSwitch 1.0 three-tier application

As you can see, a LightSwitch application is built on top of existing .NET technologies and proven architectural design patterns.

Jay

Leave a Comment
  • Please add 2 and 2 and type the answer here:
  • Post
  • The vendor lock-in for Internet technology based infrastructure/interfaces doesn't work any more. Lightswitch is heavily based on a "rich" Silverlight experience to unfold the full potential as a big RAD tool. It should have been based on HTML5.

  • This is way cool, but I was doing this in the mid-80s with Clarion. Have you looked at that product? You could learn something.

  • Tempting...but there are better ways to do this... www.alphasoftware.com  Alpha 5

  • For the presentation layer is it possible to use HTML without Silverlight (we need the site to be able to run on iPad and Android tablets)?

  • Is there a Update to this series with VS/LS - 2012 details ???

  • @LiveFromRaleigh - The "UPDATE: In Visual Studio 2012.." links we added above describe the new architecture of the OData stack in VS2012 as well as the HTML client we added in update 2. You can also visit this page for more details on the new deployment models etc: msdn.microsoft.com/.../gg491708

    Cheers!

Page 2 of 2 (21 items) 12