Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
We Make Work Software Work™
Software-as-a-Service – What’s So Great?
Siebel CRM 1999 Salesforce CRM TODAY!
Software-as-a-Service
• Pros:
• Automatically updated and upgraded
• Network effect
• Cons:
• Have to pay up front for lar...
Containers-as-a-Service
• Runs in your data center
• Runs in your private cloud
• Abstracts out operating system
• Manages...
Kubernetes Changes the Deployment Game
• No more complicated
installation process
• No more ensuring
dependencies are corr...
Containers-as-a-Service:
Vendor Manages App, Customer Owns Data
• Especially in the EU!
Why Containers-as-a-Service are the Future
Deploying as a Hybrid Cloud
Using Micro Containers for Micro Services
• Your own private Amazon
Lambda
• Services are inherently scalable
• New apps c...
The Near Future
• Instead of buying SaaS,
companies will buy services
that they add to their OWN
cloud
• New apps can be c...
From SaaS to Containers: The next phase of software delivery
Upcoming SlideShare
Loading in …5
×

From SaaS to Containers: The next phase of software delivery

The last 15 years of business software has been dominated by new SaaS services in every category from sales to customer service to finance. However, SaaS has created problems as well, such as making it hard to access your own data via APIs, security issues, difficulty to integrate across systems, and operating expense accounting. Can Containers potentially solve these problems while still retaining the benefits of SaaS over the previous generation of on-premise software?

  • Be the first to comment

  • Be the first to like this

From SaaS to Containers: The next phase of software delivery

  1. 1. We Make Work Software Work™
  2. 2. Software-as-a-Service – What’s So Great? Siebel CRM 1999 Salesforce CRM TODAY!
  3. 3. Software-as-a-Service • Pros: • Automatically updated and upgraded • Network effect • Cons: • Have to pay up front for large contracts • Opex instead of Capex affects EBITDA • No control of data • APIs are cumbersome and expensive • Delegated security • Multitenant
  4. 4. Containers-as-a-Service • Runs in your data center • Runs in your private cloud • Abstracts out operating system • Manages workflow between dev, stage, prod • Deployable via Kubernetes
  5. 5. Kubernetes Changes the Deployment Game • No more complicated installation process • No more ensuring dependencies are correct • Revolutionized versioning and upgrades
  6. 6. Containers-as-a-Service: Vendor Manages App, Customer Owns Data • Especially in the EU!
  7. 7. Why Containers-as-a-Service are the Future
  8. 8. Deploying as a Hybrid Cloud
  9. 9. Using Micro Containers for Micro Services • Your own private Amazon Lambda • Services are inherently scalable • New apps can be constructed from mix of micro services
  10. 10. The Near Future • Instead of buying SaaS, companies will buy services that they add to their OWN cloud • New apps can be composed of microservices hosted as microcontainers • Data can be easily aggregated and cross- referenced without complicated ETL

    Be the first to comment

    Login to see the comments

The last 15 years of business software has been dominated by new SaaS services in every category from sales to customer service to finance. However, SaaS has created problems as well, such as making it hard to access your own data via APIs, security issues, difficulty to integrate across systems, and operating expense accounting. Can Containers potentially solve these problems while still retaining the benefits of SaaS over the previous generation of on-premise software?

Views

Total views

424

On Slideshare

0

From embeds

0

Number of embeds

5

Actions

Downloads

6

Shares

0

Comments

0

Likes

0

×