ARCH-14: Architecting for Software as a Service Mike Ormerod Architect & OpenEdge Evangelist Colleen...
-
Upload
leslie-jocelyn-wilson -
Category
Documents
-
view
216 -
download
3
Transcript of ARCH-14: Architecting for Software as a Service Mike Ormerod Architect & OpenEdge Evangelist Colleen...
ARCH-14: Architecting for Software as a Service
Mike OrmerodArchitect & OpenEdge Evangelist
Colleen SmithDirector, Software as a Service
© 2006 Progress Software Corporation2ARCH-14: Architecting for Software As A Service
Agenda
Market Trends Technical Principles of SaaS SaaS and the OpenEdge® Reference
Architecture Case Studies
© 2006 Progress Software Corporation3ARCH-14: Architecting for Software As A Service
Client/Server -- Driven by business demands for decentralization,
flexibility and cheaper platforms.
ASP Model -- Driven by VCs’ looking to drive
more predictable revenue streams and IT vendors
looking to disintermediate traditional outsourcing
firms
SaaS 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
Early- to Mid-1990’s
Late 1990’s to 2004
2005 to 2010
…business drivers and user expectations have shifted from wanting broad applications to specialized vertical applications
Source AMR Research SaaS Study 2005
SaaS Waves and the Value Curve
© 2006 Progress Software Corporation4ARCH-14: Architecting for Software As A Service
"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] AppExchange make clear, every true SaaS 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
InfoWorld : March 2006
© 2006 Progress Software Corporation5ARCH-14: Architecting for Software As A Service
Characteristics of SaaS – A Definition
Central management of services – The SaaS 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”– SaaS 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)
© 2006 Progress Software Corporation6ARCH-14: Architecting for Software As A Service
Agenda
Market Trends Technical Principles of SaaS SaaS and the OpenEdge Reference
Architecture Case Studies
© 2006 Progress Software Corporation7ARCH-14: Architecting for Software As A Service
Multi-tenancy
Customer ACustomer ACustomer BCustomer B Customer CCustomer C Customer DCustomer D
Business Logic = Single Code Set
A B DC
Single Server
…
Shared
Controls
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
BB
B
© 2006 Progress Software Corporation8ARCH-14: Architecting for Software As A Service
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!
User Interface Freedom
Access to applications
OpenEdge
User Interface
Service Adapter
Server Service Interface
Business Logic
HTML
User Interface
Service Adapter
AJAX
User Interface
Service Adapter
Flash
User Interface
Service Adapter
Web
Services
Service Adapter
© 2006 Progress Software Corporation9ARCH-14: Architecting for Software As A Service
Technical Principles of SaaS
Full Service Delivery• Support & Monitoring
• Availability– 24x7x365
• Data Replication– Local/Remote
• Business Continuity– Reliability 24x7x365
• Continuous Product Enhancement
© 2006 Progress Software Corporation10ARCH-14: Architecting for Software As A Service
• Support for Web Services • Support for Sonic• Fast Development of New Services
Integration Enabled
Application components as services
Sonic Enterprise Service Bus
OpenEdge SQLServerOracleOpenEdge
Mainframe.NETJ2EEOpenEdgeOpenEdge
SonicOrchestration
Server
ApamaEvent Stream
Processing
Mainframe.NETJ2EEOpenEdge OpenEdge
BusinessActivity
Monitoring
© 2006 Progress Software Corporation11ARCH-14: Architecting for Software As A Service
Agenda
Market Trends Technical Principles of SaaS SaaS and the OpenEdge Reference
Architecture Case Studies
© 2006 Progress Software Corporation12ARCH-14: Architecting for Software As A Service
Shift from Business Applications to Services
Buying Transforming Selling buyerssuppliers
company business processes
…resulting in software that reflects business processes
basic software functionality is designedto address business requirements…
…constructed as modular services…
© 2006 Progress Software Corporation13ARCH-14: Architecting for Software As A Service
A SaaS Application Requires
3 Strategic Elements
A Process Centric Design
SOAEnabled
User Interface Freedom
Separation of Business
Logic/Process
© 2006 Progress Software Corporation14ARCH-14: Architecting for Software As A Service
Separated presentation
and integration layers
Data accessabstracted from
storage
Common business logic with
advanced models
OpenEdge Reference Architecture - A Blueprint for developing service-oriented business applications
How Do You Get There?
PresentationPresentation
Business ServicesBusiness Services
Data AccessData Access
Data SourcesData Sources
Enterprise ServicesEnterprise Services Co
mm
on
Infrastru
cture
Co
mm
on
Infrastru
cture
© 2006 Progress Software Corporation15ARCH-14: Architecting for Software As A Service
SaaS & the OpenEdge Reference Architecture
Customer ACustomer ACustomer BCustomer B Customer CCustomer C Customer DCustomer D
Business Logic = Single Code Set
A B DC
Single Server
…
Shared
Controls
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
Customer ACustomer A
BB
B
Increase AppServer
AgentsLoad Balancing
OpenEdge Replication
Data AccessData Access
Co
mm
on
Infrastru
cture
Co
mm
on
Infrastru
cture
© 2006 Progress Software Corporation16ARCH-14: Architecting for Software As A Service
Products for SaaS
WebSpeed, WebClient
OpenClient
Sonic Orchestration
OpenEdge Core Services
OpenEdge Management
Web Services Adapter
OpenEdge ABL
AppServer
WebSpeed Server
OpenEdge Database
Sonic MQ,
Sonic ESB
OpenEdge Replication,
Data Direct
PresentationPresentation
Business ServicesBusiness Services
Data AccessData Access
Data SourcesData Sources
Co
mm
on
Infrastru
cture
Co
mm
on
Infrastru
cture
Enterprise ServicesEnterprise Services
© 2006 Progress Software Corporation17ARCH-14: Architecting for Software As A Service
1. More Compelling User InterfaceApplication needs/features with sizzle
2. Better Integration Strategy More open, inexpensive, repeatable and flexible
3. More Agile, Flexible, Easily Modifiable ApplicationEasy to add new features and functionality
4. Disconnected / Remote Access StrategyOn-road sales reps., local caching etc.
5. Better Deployment, Servicing SystemDeploy to large number of users, easily pinpoint service difficulties
SaaS re-architecting Opportunities
Application Requirements
© 2006 Progress Software Corporation18ARCH-14: Architecting for Software As A Service
Agenda
Market Trends Technical Principles of SaaS SaaS and the OpenEdge Reference
Architecture Case Studies
© 2006 Progress Software Corporation19ARCH-14: Architecting for Software As A Service
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
© 2006 Progress Software Corporation20ARCH-14: Architecting for Software As A Service
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.
© 2006 Progress Software Corporation21ARCH-14: Architecting for Software As A Service
Case Study – Personalization- ePropertyTax
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
© 2006 Progress Software Corporation22ARCH-14: Architecting for Software As A Service
Case Study – Personalization - ePropertyTax
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
© 2006 Progress Software Corporation23ARCH-14: Architecting for Software As A Service
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
© 2006 Progress Software Corporation24ARCH-14: Architecting for Software As A Service
Case Study –Full Service- FARA Business Systems
RESULTS:• 24x7x365 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….
© 2006 Progress Software Corporation25ARCH-14: Architecting for Software As A Service
In Summary
SaaS is disrupting the industry, offering large opportunity/potential
Design and Architect your applications with SaaS built in
OpenEdge Reference Architecture supports SaaS
© 2006 Progress Software Corporation26ARCH-14: Architecting for Software As A Service
Questions?
© 2006 Progress Software Corporation27ARCH-14: Architecting for Software As A Service
Thank you foryour time
© 2006 Progress Software Corporation28ARCH-14: Architecting for Software As A Service