ARCH14 Architecting for Software as a Service Mike

ARCH-14: Architecting for Software as a Service Mike Ormerod Colleen Smith Architect & Open. Edge Evangelist Director, Software as a Service

Agenda § Market Trends § Technical Principles of Saa. S § Saa. S and the Open. Edge® Reference § Architecture Case Studies ARCH-14: Architecting for Software As A Service 2 © 2006 Progress Software Corporation

Saa. S Waves and the Value Curve Early- to Mid-1990’s Client/Server -- Driven by business demands for decentralization, flexibility and cheaper platforms. 2005 to 2010 Late 1990’s to 2004 ASP Model -- Driven by VCs’ looking to drive more predictable revenue streams and IT vendors looking to disintermediate traditional outsourcing firms Saa. S Model -- Driven by buyers looking to bypass IT backlogs, IT control, upgrade nightmares, and to avoid long-term, inflexible, and costly commitments FOCUS has shifted to buyer value drivers Source AMR Research Saa. S Study 2005 …business drivers and user expectations have shifted from wanting broad applications to specialized vertical applications ARCH-14: Architecting for Software As A Service 3 © 2006 Progress Software Corporation

Info. World : March 2006 "The ultimate disruptive effect of the 'services wave' may well resemble that of the dot-com era, when companies that were smart about leveraging the Web exploited unforeseen growth opportunities. As the viral growth of Web 2. 0 mash-ups and walled gardens like [salesforce. com's] App. Exchange make clear, every true Saa. S application is potentially part of an XML-driven ecosystem. The SMBs that figure out how to tap into the power of those ecosystems could become the enterprises of tomorrow. " - Eric Knorr ARCH-14: Architecting for Software As A Service 4 © 2006 Progress Software Corporation

Characteristics of Saa. S – A Definition § § Central management of services – The Saa. S applications are hosted, managed, and maintained in a centralized data center offering access to its applications/services via the Internet and a Web-based interface. Application Accessibility – Policy-driven configuration and personalized customization, giving users the ability to have control over how the application is used, rather than how it is implemented. A one-to-many service- In order to accomplish the “economies of scale”– Saa. S requires a multi-tenant application that supports multiple end-users accessing a single source of the application business logic and database. Guaranteed performance and reliability via service level agreements - delivery of contracted services with a guarantee that certain metrics are met. (accessibility, reliability, and overall throughput or performance) ARCH-14: Architecting for Software As A Service 5 © 2006 Progress Software Corporation

Agenda § Market Trends § Technical Principles of Saa. S § Saa. S and the Open. Edge Reference § Architecture Case Studies ARCH-14: Architecting for Software As A Service 6 © 2006 Progress Software Corporation

Multi-tenancy Customer ACustomer A Customer A Customer B Customer C Customer D … Business Logic = Single Code Set Single Server A B B Shared B B ARCH-14: Architecting for Software As A Service C D Controls 7 © 2006 Progress Software Corporation

User Interface Freedom Access to applications User Interface Freedom • to deploy the interface of choice • to construct or define user interfaces • to personalize by user group • to operate without a user interface! Open. Edge HTML AJAX Flash Web User Interface Services Service Adapter Service Adapter Service Interface Business Logic ARCH-14: Architecting for Software As A Service 8 © 2006 Progress Software Corporation

Technical Principles of Saa. S § Full Service Delivery • Support & Monitoring • Availability – 24 x 7 x 365 • Data Replication – Local/Remote • Business Continuity – Reliability 24 x 7 x 365 • Continuous Product Enhancement ARCH-14: Architecting for Software As A Service 9 © 2006 Progress Software Corporation

Integration Enabled Application components as services • Support for Web Services • Support for Sonic • Fast Development of New Services Business Activity Monitoring Sonic Orchestration Server Apama Event Stream Processing Sonic Enterprise Service Bus Open. Edge J 2 EE . NET Open. Edge Oracle SQL Server Open. Edge ARCH-14: Architecting for Software As A Service Mainframe 10 © 2006 Progress Software Corporation

Agenda § Market Trends § Technical Principles of Saa. S § Saa. S and the Open. Edge Reference § Architecture Case Studies ARCH-14: Architecting for Software As A Service 11 © 2006 Progress Software Corporation

Shift from Business Applications to Services basic software functionality is designed to address business requirements… …constructed as modular services… …resulting in software that reflects business processes company business processes suppliers Buying Transforming Selling ARCH-14: Architecting for Software As A Service buyers 12 © 2006 Progress Software Corporation

A Saa. S Application Requires A Process Centric Design Separation of User Business Interface Logic/Process Freedom SOA Enabled 3 Strategic Elements ARCH-14: Architecting for Software As A Service 13 © 2006 Progress Software Corporation

How Do You Get There? Open. Edge Reference Architecture - A Blueprint for developing service-oriented business applications Common business logic with advanced models Data access abstracted from storage ARCH-14: Architecting for Software As A Service Enterprise Services Business Services Data Access Data Sources Common Infrastructure Separated presentation and integration layers Presentation 14 © 2006 Progress Software Corporation

Saa. S & the Open. Edge Reference Architecture Customer ACustomer A Customer B Customer A Increase App. Server Customer A Agents Customer C Customer D Load Balancing Common Infrastructure Business Logic = Single Code Set Data Access Single Server A B B Shared B B … C D Controls Open. Edge Replication ARCH-14: Architecting for Software As A Service 15 © 2006 Progress Software Corporation

Products for Saa. S Web Services Adapter Sonic MQ, Sonic ESB Web. Speed, Web. Client Open. Client Enterprise Services Sonic Orchestration Business Services Data Access Open. Edge ABL App. Server Web. Speed Server Open. Edge Database Open. Edge Replication, Data Sources Common Infrastructure Presentation Open. Edge Core Services Open. Edge Management Data Direct ARCH-14: Architecting for Software As A Service 16 © 2006 Progress Software Corporation

Saa. S re-architecting Opportunities Application Requirements 1. More Compelling User Interface 2. Better Integration Strategy 3. More Agile, Flexible, Easily Modifiable Application 4. Disconnected / Remote Access Strategy 5. Better Deployment, Servicing System Application needs/features with sizzle More open, inexpensive, repeatable and flexible Easy to add new features and functionality On-road sales reps. , local caching etc. Deploy to large number of users, easily pinpoint service difficulties ARCH-14: Architecting for Software As A Service 17 © 2006 Progress Software Corporation

Agenda § Market Trends § Technical Principles of Saa. S § Saa. S and the Open. Edge Reference § Architecture Case Studies ARCH-14: Architecting for Software As A Service 18 © 2006 Progress Software Corporation

Case Study- Multi-tenancy/security- KCS § § GOALS: • Provide customers with comprehensive HR/ Payroll applications – Multiple market segments • Assume the day-to-day management responsibility – provide improved control of the data and application/management reports • Overcome the concern about data security, stability and reliability HOW: • Security control system - database update, enquiry, at field/user level – Access and update controls established by user, department, cost centre, office, company or total database; or by employee type, grade, or position • Self-service Portal –allows employees to update information for themselves, manage and query their own data • 'Sets' facility which allows for creation of employee records for individual tasks • Input data directly -allowing anytime, anywhere input from one source, regional or line management • Integrated modular solution – the core personnel administration database can be accessed by a number of optional bolt-on components ARCH-14: Architecting for Software As A Service 19 © 2006 Progress Software Corporation

Case Study- Multi-tenancy/security- KCS § RESULTS: • Chose a hosting partner where the infrastructure they operate with is completely secure - uses biometric technology for access and the building is as inherently secure as the data. • Leverage a multi-tenanted system for hosting multiple end user customers that all log into the same ISP. • Foster a high degree of confidence through growth achieving a 10% increase in annual revenue • Offer a full menu of options and supply both sides of the process - providing whatever range of technology services are required and help adapt to business changes. ARCH-14: Architecting for Software As A Service 20 © 2006 Progress Software Corporation

Case Study – Personalization- e. Property. Tax § § GOALS: • To be both a software technology and a property tax service company • Design a service plan for each customer around needs and requirements • Continuously provide updates and maintain valuable property tax content, without customer involvement • Create a shared resources environment more powerful and scalable than any single customer configuration. • Allow customers to own their own data, and remove it at anytime. HOW: • Architected a hosted solution with a focus on Customer personalization using Web Speed • Handle scalability and volume using 6 Brokers and 2 app servers • Update product features weekly and apply tax changes yearly to single code base • Provide user permissions at a function level – with field level security - all data logically segregated by company ID – set up Queries with Company ID ARCH-14: Architecting for Software As A Service 21 © 2006 Progress Software Corporation

Case Study – Personalization - e. Property. Tax § RESULTS: • Property Tax Office® is an open platform that allows customers to choose anyone to service their property taxes. • A fully Web-native software application, delivered through the Internet, with the best cost/benefit relationship in the marketplace • Designed and implemented the first automated and digitally monitored quality control process for property tax compliance. • Give customers real-time visibility of the status of every tax bill, assessment, and personal property tax return that we are processing, providing constant assurance of on-time quality service • Pricing – per property managed ARCH-14: Architecting for Software As A Service 22 © 2006 Progress Software Corporation

Case Study – Full-Service– FARA Business Systems § § GOALS: • To provide insurance/risk management related services to insurance companies • Increase revenue per associate -utilizing the latest cost effective technologies • Perform application management, support, backup/restore, and Disaster Recovery • Ability to keep cost and disruption very LOW…with accessibility very HIGH HOW: • Develop a single code set with a single common database with segmentation at the company level • Provide access via a web browser – not “n-tiered” • Added value comes in the form of additional IT support for app mgmt, backup/restore with a focus on DR. • Little customization – more focus on the “like” business processes • Creating new products- based off of the “core” product –new users ARCH-14: Architecting for Software As A Service 23 © 2006 Progress Software Corporation

Case Study –Full Service- FARA Business Systems § RESULTS: • 24 x 7 x 365 claim reporting system with immediate claim confirmation and assignment • Web access to claim progress notes, reserves, payments, digital images, etc. • Business intelligence to manage each claim to a low-cost, high satisfaction result. • Application delivered as a service is up and running in 60 days or less • Provides quarterly new features with weekly updates/fixes – performs pre-test and have rollback capabilities • Meets all security needs – has knowledge of what is needed in the industry and provides for it…. ARCH-14: Architecting for Software As A Service 24 © 2006 Progress Software Corporation

In Summary § Saa. S is disrupting the industry, § § offering large opportunity/potential Design and Architect your applications with Saa. S built in Open. Edge Reference Architecture supports Saa. S ARCH-14: Architecting for Software As A Service 25 © 2006 Progress Software Corporation

Questions? ARCH-14: Architecting for Software As A Service 26 © 2006 Progress Software Corporation

Thank you for your time ARCH-14: Architecting for Software As A Service 27 © 2006 Progress Software Corporation

ARCH-14: Architecting for Software As A Service 28 © 2006 Progress Software Corporation