Anything as a Service - Factors to Consider
- 1. Anything as a Service (XaaS) – Factors to Consider Stephen Newell Client Technical Advisor –Illinois Public Sector IBM Corporation srnewel@us.ibm.com
- 2. Since 2009
- 4. 2009 2014 Hype declining
- 5. 2010 2011 2012 2013 2014 #1 Cloud Cloud #2 Cloud #3 Cloud #4 Cloud #5 Annual NASCIO State CIO Survey Priority Technologies Top priority
- 6. And, in Illinois -it’s the law
- 7. Based on Federal guidelines
- 8. Anything as a Service (XaaS) XaaSis the essence of cloud computing, and these days almost anything can be delivered as a service: software, infrastructure, storage, platforms, data, you name it. The concept is no longer new but it’s far from settled. Challenges remain in building the business case and determining the risks and rewards. This session explores the factors to consider when deciding if, when and how to pull the trigger. Today
- 9. The Good The Bad SaaS Business/ Productivity Tools Minimal staffing Ready to use Browser / app/ API Mobile Predefined service SaaS silos Integration Lock-in Waiton outage PaaS Innovative/ Programmability Leverage APIs / Sell APIs Social/ Mobile DevOps Constrainedby stack Expensive at scale Lock-in Throttled Wait on outage IaaS Control / ResourceProvisioning Performance / scale / transactions Sensitive data / regulatory compliance Support complex integration Designto avoid outage Limited configurations Moreskills / new skills More staff Beware of porting existing Considerations -service models Note: None of these are hard and fast. Taking best case for The Good.Taking worst case for The Bad
- 10. The Good The Bad Public Low cost Simple and quickto start •Easy to buy •No contract Minimal staffing Unlimited scaling SLAsnot sufficient Provider supply chain Network performance No control / transparency Securityconcerns Limited flexibility Exit strategy Hybrid Use private for sensitivedata Use public as much as possible Choice and flexibility Interconnect multiple clouds Mismatchof toolsets / security More complex Community Lower costdue to larger scale Shared service Governance effort Coordination effort Private Behind your firewall Single tenant Control •Security •Compliance •D/R •Configurations Higher cost Facilities investment Capacity ceiling Upfront investment Time to establish / build Administration cost Considerations -deployment models Note: None of these are hard and fast. Taking best case for The Good.Taking worst case for The Bad
- 11. Example Private community cloud for state public sector entities Hosted and administered in two (for D/R) state data centers Runs on state network Complies with state security standards plus compliance for each workload Offered by California Department of Technology Office of Technology Services (OTech) Infrastructure supplied and managed by a cloud service vendor(IBM). Otech manages all other aspects of the offering. Custom architecture to fit with state IT tools and processes. Usage based with no initial cost to the state. IaaSnow. PaaS / DaaS / STaaS next. SaaS third. Up to 70% lower cost than current rates. Details at: http://www.servicecatalog.dts.ca.gov/services/cloud/calcloud/overview.html
- 12. Considerations -moving forward Create a vision / policy / strategy / roadmap Establish governance Lead the organizational change Select a partner Think big. Start small.
- 13. Range of offerings –our suite of offerings give us many ways to implement your strategy IaaS/ PaaS/ SaaS Private / Community / Hybrid / Public You build and manage / IBM build and manage Open standards Enterprise class –our offerings include 99.95% SLAs with disaster recovery for critical applications Control –our offerings can give you extensive control of your service Expertise–over 100,000 advisors on cloud worldwide Consulting Services IBM