Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Between the apps gluecon session 05 27-2010

Wird geladen in …3

Hier ansehen

1 von 30 Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Andere mochten auch (20)


Ähnlich wie Between the apps gluecon session 05 27-2010 (20)

Aktuellste (20)


Between the apps gluecon session 05 27-2010

  1. 1. Looking Between the Apps  What Matters to CIO’s Evaluating Cloud Services Rick Nucci Founder and CTO Boomi
  2. 2. Agenda
  3. 3. Introduction Do CIO’s Want to Move to the Cloud?
  4. 4. Quick Backdrop <ul><li>“ Wait haven’t we been doing Cloud for the last 30 years?” </li></ul><ul><ul><li>PLEASE PUT AN END TO THIS! </li></ul></ul><ul><li>Gut check: </li></ul><ul><ul><li>Most CIO’s are in “whiteboard phase” of their Cloud strategy </li></ul></ul><ul><li>Many SaaS applications deployed with no involvement or awareness from IT </li></ul><ul><ul><li>This is changing… </li></ul></ul>
  5. 5. Drivers for Change <ul><li>Lower hardware investment? </li></ul><ul><ul><li>BORING! </li></ul></ul><ul><ul><li>Not just about your Linux OS running in Amazon vs. your building </li></ul></ul><ul><li>CIO’s live with 80/20 paradox </li></ul><ul><ul><li>80% budget goes to maintenance </li></ul></ul><ul><ul><li>20% goes to innovation </li></ul></ul><ul><ul><li>THIS is real driver for change! </li></ul></ul>
  6. 6. Why 80%: “Rev Lock” Application Integration Spaghetti
  7. 7. Roots of Integration Complexity <ul><li>Closed systems + vendor priorities = API Optional </li></ul><ul><li>Just write to the database! </li></ul><ul><li>Application customization disconnected from API </li></ul><ul><li>Wildly disparate integration standards, invocation models, programming styles </li></ul>
  8. 8. Result: Executives’ Concerns about Cloud Infrastructure Services
  9. 9. The CIO’s Perspective vs. traditional SaaS purchaser
  10. 10. Top of Mind for CIO <ul><li>Debunking Hype </li></ul><ul><ul><li>Beware the Cloud Washer! </li></ul></ul><ul><li>Your application is one in a portfolio </li></ul><ul><li>Focus on business processes across many departments </li></ul>
  11. 11. Simple Process Mapping Lead Capture E-Commerce Shipping Customer Service Customer Item Lead Help Ticket Process Flow Core Entities Web Form Signup Product Purchase & Payment Product Delivery Technical Help & Returns
  12. 12. Simple Process Mapping Customer Item Lead Help Ticket Core Entities Applications E-Commerce CRM Finance/ERP Support
  13. 13. Today – SaaS Connectivity Principles <ul><li>Closed systems = No traction </li></ul><ul><li>API not optional </li></ul><ul><li>There is no database! </li></ul><ul><li>Multi-tenancy architecture forces customizations to manifest in API </li></ul><ul><li>We at least agree on a few things </li></ul><ul><ul><li>HTTPS, SOAP/WSDL, REST/WADL </li></ul></ul>
  14. 14. Today – Big Mentality Shift <ul><li>Who owns the integration problem? </li></ul><ul><li>SaaS ISV – must solve during sales cycle </li></ul><ul><li>Department purchasing SaaS: “I love your solution, show me how it connects to X” </li></ul>
  15. 15. CIO Impact on Buying Cycle
  16. 17. Key CIO Focus Areas <ul><li>Identity management </li></ul><ul><ul><li>Centralized Access Control </li></ul></ul><ul><ul><li>SSO: </li></ul></ul><ul><ul><ul><li>expect &quot;trust authority&quot; to be on-prem or saas </li></ul></ul></ul><ul><li>Enterprise mashups </li></ul><ul><ul><li>enterprise &quot;widgets&quot; to embed components of your application </li></ul></ul><ul><ul><li>lookup-style API's </li></ul></ul><ul><ul><ul><li>fast and accurate access to enterprise data and transactions </li></ul></ul></ul><ul><li>There are MANY more! </li></ul><ul><ul><li>BI, Mobile, Operations, Compliance </li></ul></ul>
  17. 19. CIO Questions <ul><li>Is your API part of your core product? </li></ul><ul><ul><li>Owned by product management? </li></ul></ul><ul><ul><li>Integrated into SDLC processes? </li></ul></ul><ul><li>Do you charge extra for your API? </li></ul><ul><ul><li>“ Oh, you wanted outlets for your electricity?” </li></ul></ul><ul><li>What is your API strategy? </li></ul><ul><ul><li>Best in class examples: </li></ul></ul><ul><ul><ul><li>“ We offer free, open access to API and documentation as part of product evaluation” </li></ul></ul></ul><ul><ul><ul><li>“ You will come up with smarter uses of our API than we will” </li></ul></ul></ul>
  18. 20. Other API Best Practices <ul><li>API Versioning </li></ul><ul><ul><li>We won’t upgrade integration when app upgrades </li></ul></ul><ul><ul><li>Version should be part of URL (ex. http://myapp.com/api/3.0) </li></ul></ul><ul><li>Query by last modified date critical </li></ul><ul><ul><li>Very common approach to capturing changed data </li></ul></ul><ul><ul><li>Key need for BI </li></ul></ul><ul><li>Ensure API has throttling and batching mechanism </li></ul>
  19. 21. Tomorrow: Transitioning to The Cloud Financials BI HRIS SaaS Application Custom Application Public Cloud SaaS Applications PaaS Application
  20. 22. Are we heading towards this again?
  21. 23. The Data Imperative <ul><li>Data transcends boundaries </li></ul><ul><li>End-to-end visibility is top priority </li></ul><ul><li>Data compliance is key </li></ul>
  22. 24. <ul><li>Everything is de-centralized </li></ul><ul><li>Integrate Everywhere </li></ul><ul><li>You need an Audit Trail </li></ul><ul><li>Centralize Development/Management </li></ul>IDE & Ops Centralization
  23. 25. <ul><li>Augment vs. “Rip & Replace” </li></ul><ul><ul><li>In line with SaaS strategy, in general </li></ul></ul><ul><li>Inefficiencies will become apparent, with greater SaaS adoption </li></ul>The Role of Traditional Middleware
  24. 27. <ul><li>Identity Integration </li></ul><ul><li>User Experience Integration </li></ul><ul><li>Process Integration </li></ul><ul><li>Data Integration </li></ul>Long Term Vision – “Virtual Suite”
  25. 28. Summary <ul><li>Strong business drivers exist for CIO Today </li></ul><ul><li>CIO’s thinking about this now </li></ul><ul><li>The way SaaS is purchased, delivered and supported will change significantly </li></ul><ul><li>This is good for all! </li></ul>
  26. 29. Thank You! Rick Nucci @ricknucci Questions?
  27. 30. Copyright © 2010 Boomi, Inc.  All rights reserved.  Boomi, Boomi On Demand, Visual Integration Platform, Atom, Integration Cloud and AtomSphere and their respective logos are the registered or common law trademarks, or service marks of Boomi, Inc. in the United States and other countries. All other trademarks and service marks used in this publication are the property of their respective owners. The contents of this presentation are confidential and should not be shared outside of the intended audience or recipient.

Hinweis der Redaktion

  • -- top of mind for CIO   debunking hype (goes for all of us) - &amp;quot;seems like a lot of the same stuff i used to buy now runs in Amazon as a &apos;cloud edition&apos;?” :: DANGER - cloudwashing dilutes real value of SaaS and Cloud and is soooo easy to do 2.  have to do this over and over again (buy a saas app) vs. LOB owner 3.  looking at cross department business processes-- deep dive into this discussion   -- there are 2-3 different departments involved even in this simple example
  • - there are 2-3 different departments involved even in this simple example
  • Identity management Standards to support and connect to on-prem directories centralized control of access to all applications storing any core enterprise data SSO: expect &amp;quot;trust authority&amp;quot; to be on-prem or saas Active Directory New cloud-based solutions need to handle user provisioning events from a central source, and need to delegate trust to central authority Enterprise mashups ability to view data from cross-departmental applications without leaving current session UI-level integration - but not plotting stuff on google maps, think &amp;quot;single view of customer” expected requirements enterprise &amp;quot;widgets&amp;quot; to embed components of your application into other sources, including SSO and context passing (i.e. &amp;quot;this is customer the widget should display&amp;quot;) lookup-style API&apos;s that provide fast and accurate access to enterprise data and transactions API Versioning
  • Data now transcends multiple networks, data centers and “ownership boundaries” End-to-end visibility of this data is top priority Provisions to prevent non-compliant data communication must be enforceable
  • Not only is data de-centralized, so are applications and integration points Integration “applets” therefore need to run in various networks, clouds, etc. to maximize efficiency and scalability Key challenge with traditional “spaghetti code” is ability to audit where integration code runs Need to centralize development and management environments is paramount to solving these challenges
  • Augment vs. “rip &amp; replace” Ensure rapid time-to-value In line with SaaS strategy in general As SaaS moves across departments and becomes centralized, issues with traditional middleware become apparent Data Imperative and Centralization not factored into their product strategy
  • -- Can Cloud deliver the best parts of the Suite model with the best parts of the Best of Breed model... :: Unified user experience :: pre-integrated application modules :: modules by vendors with deep expertise in their areas
  • -- there are strong drivers today for CIO&apos;s to adopt real cloud solutions (vs. cloud washed on prem) -- CIO&apos;s are having these broad, enterprise discussions and designs now -- CIO&apos;s will become much more active in the procurement of SaaS apps that were traditionally LOB sold and delivered -- This will change the way SaaS is purchased implemented, and operationalized -- This is a good thing for all!  Continues to move SaaS up the list of strategic assets to the CIO...