Cloud Principles

1,325 views
1,203 views

Published on

Short presentation describing various cloud integration methods and possible migration pittfalls.

Published in: Technology, Economy & Finance
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,325
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
25
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Cloud Principles

  1. 1. Cloud Principles
  2. 2. Frontend Build To Change Services Design To Last
  3. 3. Frontend Build To Change Services Design To Last Amazon Google SalesForce ERP billing
  4. 4. Cloud integration mechanisms <ul><li>Decoupled </li></ul><ul><li>Store-front </li></ul><ul><li>Inside-Out </li></ul>
  5. 5. Decoupled: Force.com Force.com SFA HRM KMS Custom Force Sites SAP initiates import and export of data. Orders in force.com are unresolved and new customers will be leads until a successful feedback of the backend is given. This mechanism is called decoupled and requires not much changes on the current IT landscape. SAP Force Sites Force Sites 1 2 3 <ul><li>Independent development of steps is possible: </li></ul><ul><li>Front-end User Interface (starting with leads) </li></ul><ul><li>Loading of customer data from your backend </li></ul><ul><li>Getting contracted updates and changes to your backend </li></ul>
  6. 6. Decoupled <ul><li>Can be implemented without backend where updates are managed manually </li></ul><ul><li>Strong separation of concern </li></ul><ul><li>Only keep parts highly available for the Internet and not for internal use (no costs) </li></ul><ul><li>No problems in maintenance and update schedules </li></ul><ul><li>Mandates an asynchronous application design. </li></ul>
  7. 7. Storefront using AWS Business Build For Change Process Build To Last CMS User (Browser) HR CRM sales DB Process Layer Online Integration (I/O) static data CDN BASIC Customer Data Content Data Site Logic
  8. 8. Storefront <ul><li>Enhances the companies webpresence by placing this in the cloud </li></ul><ul><li>Physical separation of concern </li></ul><ul><li>Very fast and scalable for content </li></ul><ul><li>Technology independent because integration is in the frontend </li></ul>
  9. 9. Example Inside-Out: Google <ul><li>Extends current application infrastructure </li></ul><ul><li>Keeps secure data out of the cloud </li></ul><ul><li>High performance infrastructure needed which can be placed in a (private) cloud </li></ul><ul><li>Extends existing service oriented mechanisms </li></ul><ul><li>Can also be used in other scenario’s as extension for the internal infrastructure. </li></ul>
  10. 10. Inside Out <ul><li>Use cloud resources when needed from inside: </li></ul><ul><ul><li>Cloudbursting (hadoop) </li></ul></ul><ul><ul><li>Surge computing (cpu on demand) </li></ul></ul><ul><ul><li>Enterprise Application Webservices </li></ul></ul><ul><li>For (more) mature IT environments </li></ul><ul><li>Scaling up performance, scale back IT </li></ul>
  11. 11. What to use? Sample of an basic architecture based on Porter’s Value Chain Let’s take Porter’s value chain as a basis……… Inbound logistics Opera tions Outbound Logistics Marketing & Sales Service Inside-Out Decoupled Store-front
  12. 12. Migration Tactics <ul><li>Slow adoption strategy Use a small feature basis and roll-out new ones weekly instead of big bang </li></ul><ul><li>Use intermediate data formats Migration data always in independent formats for rollback/alternative scenario </li></ul><ul><li>Plan company data backup (retention) </li></ul><ul><li>Network and infrastructure planning Since network connectivity is key for cloud </li></ul>

×