exploring the building of software + services applications · exploring the building of software +...

GAINING INSIGHT TOUR 2007

Exploring the Building of Software + Services

Applications

Pooya Darugar

http://blogs.msdn.com/pooyad


Introducing Software + Services

A Closer Look at Services

Building Applications in an S+S World

Agenda


Software + ServicesThe basics

• Enterprises today primarily use software that they run themselves– Commonly known as on-premises

• Software as a service (SaaS) is becoming a more important part of enterprise IT– Enterprises are moving toward a mixed world of

software + services (S+S)

• S+S = On-premises software + software as a service


Server-Service Continuum

“Pure-play SaaS”

“Traditional IT”

HybridApproach


S vs. S


FROM TO

S+S not S vs. S


Industry Adopting S+S Too…

Google CEO Says Softwareto Play a Bigger Role

"Ajax and Web 2.0 are great technologies for casual use, but for mission critical you need the capabilities of a desktop app." Greg Gianforte, CEO ,RightNow

http://www.rightnow.com/

http://www.ebay.com/


S+S, SOA, Web 2.0, …

Service Delivery

SaaS

Service Composition

SOA

Service Experience

Web 2.0

Service …

…





Agenda


Enterprise

Server Software

Desktop Software

On-premises Software

Service Provider

Server Software Services

Internet

Illustrating S+S


S+S from a development perspective

• Client – Rich client or Thin client

– Similar to your decision for Desktop vs. Web App

• Why not both?

– If you follow the principles of SOA and build around services, it’s much easier to create multiple clients (devices, …)


Illustrating S+S : Email


S+S from a hosting perspective

• On premise vs. In the cloud

• Maintenance

– Upgrades

– Deployment

– …


S + S : Hostingeg. Microsoft Exchange

Enterprise Y Enterprise Z

Microsoft

Enterprise X

Internet

On Premise

Hosted Managed

Service Provider

On Premise


S+S: Email





Agenda


Evaluating ServicesPotential benefits

• Lower costs– No up-front license to buy– Usage-based pricing is common

• Faster deployment• Less financial risk

– No large up-front investment required– Can often try before you buy

• Higher reliability– At least for some organizations

• Easier upgrades


Evaluating ServicesPotential challenges (1)

• Trust

– Can this service provider be trusted?

• Data

– How safe is it?

• Integration

– How can a SaaS application be connected with applications in the enterprise?


Evaluating ServicesPotential challenges (2)

• Customization

– How much is possible?

• Identity

– Is identity federation supported?

• Management

– How can a SaaS application be monitored?

• Supporting users

– Who runs the help desk?


The Development Decision Creating an application as on-premises software

• The application must be tested in all of the environments in which it will run– Perhaps on multiple operating systems

• The application must be installed at each customer

• Updating the application requires changing installed code at each customer’s site– Perhaps multiple copies of that code at each site

• The application’s performance and reliability depend in part on the environment in which the customer runs it– It’s out of the ISV’s control


The Development DecisionCreating an application as SaaS

• The application will run in only one environment– And so need be tested only for that environment

• The application can be immediately available to any customer with Internet access anywhere in the world– For browser-accessible applications, no installation at

customer sites is required

• Updating the application requires changing only one copy of the code

• The service provider controls the environment in which the application runs– The ISV might do this itself





Agenda


Service Provider

Computer

Single-Tenant Application

Computer


Computer


Internet

Enterprise Y Enterprise Z Enterprise X

Illustrating Single-Tenancy~ Application Service Providers (ASP)


Kinds of ServicesSingle-tenant vs. multi-tenant

• Single-tenant application:– A service provider offers a unique instance of an

application for each organization that uses it– Pros: Allows better isolation– Cons: Can be more expensive because the service provider

can’t share as much

• Multi-tenant application:– A service provider offers a shared instance of an

application for all organizations that use it– Pros: Can be cheaper– Cons: Allows less isolation


Service Provider

Computer

Multi-Tenant Application

Internet

Enterprise Y Enterprise Z Enterprise X

Illustrating Multi-Tenancy


S+S Architecture: Build

• Application Architecture

– Designing a “back end as a service”• Multitenancy vs. Isolation

• Customization: Metadata -Templatized

• Performance

• Self Service / Try before you buy

– Designing Rich “front end” • Disconnected experience

• Smart Client tenant customization

• Office as UI

• Technologies support: Dev Platform– .NET Fx 3.5 (WPF,WCF, WF), AD, AzMan, VSTO

LitwareHR


Rich Client

Offline Support

Rich Visualization

Batch Entry

Office Integration

Network

Web Client

Public Web site

Search for jobs

Apply for jobs

Public access

Secure Web Client

Private admin site

Post jobs

Search for applicants

Authenticated access

HR Application (job site)

Single instance multi-tenant

LitwareHR Demo Walkthrough


DEMO


Resources

• http://blogs.msdn.com/pooyad (My blog)

• http://www.codeplex.com/LitwareHR (Litware on Codeplex)

• http://www.codeplex.com/LitwareHR/Release/ProjectReleases.aspx?ReleaseId=6113 (LitwareSmart Client)



http://www.codeplex.com/LitwareHR

http://www.codeplex.com/LitwareHR

http://www.codeplex.com/LitwareHR/Release/ProjectReleases.aspx?ReleaseId=6113




Conclusion


FROM TO

S+S


Software + Services

Service Delivery

SaaS

Service Composition

SOA

Service Experience

Web 2.0

Service …

…

exploring the building of software + services applications · exploring the building of software +...

Documents