Enterprise Application Stores

14
3/15/22 Enterprise Application Stores

description

Enterprise Application Stores. Tuesday, February 21, 2012. Primary use cases. On boarding Migrate existing applications to cloud Fastest, most cost effective, systematic way to get on a cloud Hybrid/Federated Continuous and incremental “On boarding ” Cloud bursting No lock-in - PowerPoint PPT Presentation

Transcript of Enterprise Application Stores

Wednesday, April 19, 2023

Enterprise Application Stores

2

Primary use cases

On boardingMigrate existing applications to cloudFastest, most cost effective, systematic way to get on a cloud

Hybrid/Federated Continuous and incremental “On boarding”Cloud burstingNo lock-in Cloud protection: instance, region, vendor

Enterprise App StoreDynamic catalog image assemblyLinear vs. exponential image management

ISV distributionPre-installed, pre-configured software distributionFastest time to deploymentReusable demo/poc, pre-configured implementations

3

Enterprise App Stores

VMsprawl is a bigger problem than server sprawl

Cloud scale is all about automation

Self service is a foundational theme

Dynamic catalog image assembly

4

Large scrolling list of 800+ images is overwhelming

AND ….customers don’t

use single components - they build complete stacks

What’s the root problem an EAS is addressing?

The cloud industry’s current approach to ecosystem mgmt adds no value to published components and lacks the concept of

“bundles”

OS A32bit

OS A64bit

OS B 32bit

OS B 64bit

Partner A Partner B Partner C Partner D

Image Sprawl

Imagine a simple, early, ecosystem use-case- 2 Certified Operating Systems

- 1 Foundational element say JBoss

- 3 partner offerings, which a customer might use on their own or integrated into a WebSphere stack

Operating System- Need to cover 32 and 64 bit

- Only 1 release at the moment, what happens when new release of OS?

Partner Products- Customers might want up to 12 different combinations of these

items

- What happens as the number of partners grows?

6

OS A32bit

OS A64bit

OS B 32bit

OS B 64bit

Partner A Partner B Partner C Partner D

Sprawl the result of pre-built images?

7

OS A32bit

OS A64bit

OS B 32bit

OS B 64bit

Partner A Partner B Partner C Partner D

Our example requires 48 images

What about different version, hypervisor, cloud vectors

Data Tables

Image Catalog

Deployment

BaseOwner : Infrastructure

Monitoring

Storage

Security

Backup

Database

Biz Logic

UI

Presentation

App logic

Workflow

WorkloadOwner : App Dev, DBA

Windows

Solaris

OSOwner : Sys Admin

Linux

App Server

Database

Messaging

Process

MiddlewareOwner : Infrastructure, DBA

Operational stacks and “images”

None

Dynamic composition

Dynamic composition

Frictionless dynamic composition

11

How the enterprise consumes applications

Use cases:Cloud catalog - Dynamic composition OS+Mgmt+Srvs+App

Telcos services offering for SMB or Public

Apps operations offering for company function – F&A, Dev, Sales

Streamlined ISV delivery

Flexible, loosely coupled set of components:Purpose fronted – Store canvas or front end

Repository/Catalog – Where images/apps are stored

Provisioning engine – Life cycle manager

Operational stacks – Where the apps run i.e. Cloud

12

Enterprise App Store (EAS)

Repository

Private

TelcoPublic Open

Stack

IWD

HP

BSA

Elastic Server

Operational Stacks

Automation

13

Enterprise App Store (EAS)

CloudSprawl is a bigger problem than server sprawl or VMsprawl

Simplified mage selection

Self-service, on-demand provisioning of server apps

No cloud lock-in

Operational efficiency at cloud scale

Standardize and automate configurations

Easy add-in model

Dynamic catalog image assembly

14

Demo: Migrating Apps to the Cloud

My Enterprise App StoreThe Cloud

Windows Server