DZone
Cloud Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Cloud Zone > The Changing Cloud Developer Experience

The Changing Cloud Developer Experience

Chris Haddad user avatar by
Chris Haddad
·
Jun. 05, 12 · Cloud Zone · Interview
Like (0)
Save
Tweet
1.54K Views

Join the DZone community and get the full member experience.

Join For Free

PaaS and DevOps tooling is an opportunity to raise infrastructure abstraction.  DevOps tooling integrated with PaaS should shield developers from hardware infrastructure concerns and expose business entities.  The Cloud washed PaaS environments commonly do not shield application developers, integrators, and architects from infrastructure details (i.e. memory configuration, location, number of machine instances). While short-term benefit is derived by ‘quickly pushing bits into the Cloud’, the design and development experience remains the same.

Figure 1 illustrates how platforms can create abstraction levels on top of traditional infrastructure and shield developers from complexity.

Figure 1: PaaS Abstrations and Complexity

PaaS Abstractions

How can PaaS simplify the application platform?

 

With both the hardware infrastructure and application platform abstraction levels, teams can often forklift existing applications into the Cloud with few modifications.  The migrated applications will run in the Cloud, but will not be purpose-built for the Cloud. If teams desire to obtain Cloud benefits by delivering business capabilities ‘as a service’, business entities should be exposed, composed, connected, consumed, and orchestrated as services.  A business entity perspective is required to decompose applications and flexibly distribute the entities across Cloud nodes.

PaaS environments exposing APIs, services, and communication channels deliver application building blocks at an abstraction level that accelerates application development. Developers natively interact with APIs instead of objects, and easily provision personalized end-user workspaces.  With a Cloud Native PaaS, multi-tenancy is extended inside the application, and tenancy can be applied to users, workspaces, and transactions. Also, application scalability, isolation and partitioning are achieved through stateless distributed components as opposed to tight session replication and deployment silos.

At which platform abstraction level would you rather spend your time?

WSO2 Stratos delivers business entity level abstractions.

Cloud dev application

Published at DZone with permission of Chris Haddad, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • This Is How You Give Good Feedback at Work
  • A First Look at CSS When and Else Statements
  • Building a Login Screen With React and Bootstrap
  • How to Upload/Download a File To and From the Server

Comments

Cloud Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo