Category Archives: Platform as a Service

Four Point DevOps Story

Build team interest and passion in DevOps by promoting four DevOps themes:

  1. DevOps PaaS Delivers at the Speed of Business Demand
  2. DevOps Equals DevOps Principles Plus DevOps Practices
  3. The Agile DevOps PaaS Mindset
  4. ALM PaaS Bridges the Dev Gap

Every team member desires to fulfill their objective while delivering  at the Speed of Business DemandHigh performance IT teams move at the speed of business.

They rapidly deliver high quality software solutions that enable business penetration into new markets, create innovative products, and improve customer experience and retention. Unfortunately, most IT teams do not have an environment fostering the rapid iteration, streamlined workflow, and effective collaboration required to operate at the speed of now and capture business opportunity. Disconnected tooling, static environment deployment, and heavyweight governance across development and operations often impede rapid software cycles, minimize delivery visibility, and prohibit innovative experimentation.

A new, more responsive IT model is required!  

A more responsive IT model incorporates  DevOps Principles Plus DevOps Practices.

Every successful, long-lasting model has a clear manifesto outlining goals and principles. Many DevOps adopters may not be aware of the DevOps Manifesto (created by Jez Humble @jezhumble) nor how successful DevOps requires keeping a clear focus on principles, practices, and value (instead of infrastructure tooling.

When teams converge agile and DevOps practices with Platform-as-a-Service (PaaS) infrastructure, they adopt an agile DevOps PaaS mindset.  They create a collaborative environment that accelerates business enablement and increases customer engagement. Adopting agile devops requires a structural mind shift, and successful IT teams follow manifesto guidance to change delivery dynamics, take small steps to build one team, focus on real deliverables, accelerate reactive adaptation, and guide continuous loop activity.

Effective cross-functional teams drive every big success. Whether bridging dev with ops or biz with dev, encourage self-organizing teams and value small daily interactions.

ALM PaaS bridges the development gap between corporate IT and distributed outsourced development activities. The traditional gap impedes system integration, user acceptance testing, visibility into project progress, and corporate governance. Stephen Withers describes an often true, and ineffective current ALM state:

” the CIO does not have visibility of the overall project: this is a major problem.”

A top CIO desire is to obtain portfolio-wide visibility into development velocity, operational efficiency, and application usage.

What solution or best practices do you see solving balkanized, silo development tooling, fractured governance, disconnected workflow, and incomplete status reporting when working with distributed outsourced teams or across internal teams?

Recommended Reading

  1. DevOps PaaS Delivers at the Speed of Business Demand
  2. DevOps Equals DevOps Principles Plus DevOps Practices
  3. The Agile DevOps PaaS Mindset
  4. ALM PaaS Bridges the Dev Gap

 

Infrastructure Services Model Layers

Infrastructure Cloud Services Model

Cloud API popularity is fueling interest in creating service ecosystems across organizations, teams, and applications.  By externalizing software platform functions from containers, operating systems, and on-premise data center environments, new business opportunities emerge, and development teams gain faster time to market when building scalable business solutions. Is the time right for you to build a cloud ecosystem architecture  based on APIs and supporting rapid application development?

Continue reading

pressreleasepoint.com.shadowIT

Embrace Shadow IT Clouds

Cloud is the new shadow IT for enterprises. While stable, well-known SaaS offerings such as Salesforce or Netsuite are excellent paths forward,  unregulated, shadow IT cloud deployments often expand  business risk and magnify IT inefficiencies.   According to a recent TechRepublic report, shadow IT departments can create major fiscal problems for businesses using the cloud.  A PressReleasepoint.com release points to the source of increasing shadow IT cloud deployments:

Leasing cloud servers and subscribing to applications is incredibly easy. There is no reason why a business manager, customer service representative or other non-technical employee cannot quickly establish a cloud deal and start using an application because he or she thinks it will get the job done effectively. This is precisely why IT oversight is necessary.

Shadow IT teams gain faster time to market and decrease delivery hurdles by running home-brewed business critical systems on AWS, Heroku, Cloudbees, Azure and other cloud platforms. Often enterprise IT only discovers Cloud systems existence when the Shadow IT project requires access to  enterprise system data or services.

To co-exist with Shadow IT and maximize Cloud efficiency and productivity,  align corporate IT policy, architecture, operations, and support with innovative, shadow IT projects . Are you an expert at working with Shadow IT?

Continue reading

FedRamp

Federal Systems Integrator Advantage

A system integrator serving the U.S. Federal government market is reviewing next-generation architecture components and middleware platform technology, leading best practices, and vendor support.  The goal is to provide the system integrator with a competitive edge in re-competes and new project wins.  The desired middleware infrastructure platform will reduce development and run-time operation cost by at least 25% when compared with incumbent platform offerings.

According to the U.S. Government Accountability Office (GAO),

For decades, DOD has been attempting to modernize about 2,200 business systems, which are supported by billions of dollars in annual expenditures that are intended to support business functions and operations.

Can government IT programs and projects increase their  efficiency and reduce expenditures?   A new software delivery paradigm is required.

WSO2 is an open source middleware vendor with innovative components that help teams obtain repeatable agile delivery and adopt SOA & DevOps best practices leading to faster program spirals. Additionally, WSO2’s middleware infrastructure platform delivers high performance at high transaction rates while securely capturing, streaming, transforming, analyzing, and presenting mission information.

The system integrator is exploring three specific focus areas:

  • Information Hub Attribute Based Access Control
  • Enhance mission situational awareness and improve information transfer efficiency
  • Deliver High Quality Solutions on Faster Spirals

Continue reading

WSO2 App Factory

DevOps PaaS delivers at the speed of business demand

High performance IT teams move at the speed of business. They rapidly deliver high quality software solutions that enable business penetration into new markets, create innovative products, and improve customer experience and retention.  Unfortunately, most IT teams do not have an environment fostering the rapid iteration, streamlined workflow, and effective collaboration required to operate at the speed of now and capture business opportunity. Disconnected tooling, static environment deployment, and heavyweight governance across development and operations often impede rapid software cycles, minimize delivery visibility, and prohibit innovative experimentation.

A new, more responsive IT model is required.

Continue reading

Apache Stratos

Why Apache Stratos

Apache Stratos  is an Open Platform as a Service (PaaS) framework project supported by the Apache community.  Apache Stratos brings enterprise-ready quality of service, governance, security, and performance to internal private clouds, externally managed clouds, and public clouds. Enterprise organizations, Cloud infrastructure vendors, and Cloud service providers may freely modify, distribute, and deploy Apache Stratos without any intellectual property restrictions, royalties, or fees.

Continue reading

WSO2 App Factory

The Agile DevOps PaaS mindset

When teams converge agile and devops practices with Platform-as-a-Service (PaaS) infrastructure, they create a collaborative environment that accelerates business enablement and increases customer engagement. Adopting agile devops requires a structural mind shift, and successful IT teams follow manifesto guidance to change delivery dynamics, take small steps to build one team, focus on real deliverables, accelerate reactive adaptation, and guide continuous loop activity.

Continue reading

Collaborative

ALM PaaS Bridges the Dev Gap

ALM PaaS bridges the development gap between corporate IT and distributed outsourced development activities.  The traditional gap impedes system integration, user acceptance testing, visibility into project progress, and corporate governance. Stephen Withers describes an often true, and ineffective current ALM state:

” the CIO does not have visibility of the overall project: this is a major problem.”

A top CIO desire is to obtain portfolio-wide visibility into development velocity, operational efficiency, and application usage.

What solution or best practices do you see solving balkanized, silo development tooling, governance, workflow, and status reporting across distributed outsourced teams?  Does your desired solution integrate with tools a CIO’s outsourced organizations  are using?

Continue reading

Home Port Lighthouse - Galle

From the Home Port Lighthouse

The crew in the Home Port Lighthouse spotted a few interesting posts were spotted.   Here are the links and my sighting report:

Location: CloudBees Cloud App Development Platform Available on Verizon Cloud
WSO2 App Factory is an Open Source PaaS offering functionality similar to CloudBees. The DevOps PaaS delivers Jenkins, continuous delivery, enterprise governance, and DevOps best practices.

 

Location: Harnessing the Power of APIs
Are you publishing Naked APIs, or Managed APIs?  A managed API is:

  • Actively advertised and subscribe-able
  • Available with an associated, published service-level agreement (SLA)
  • Secured, authenticated, authorized and protected
  • Monitored and monetized with analytics

When creating an API Management program, consider including these five steps:

  • Step 1 Embrace the Managed API
  • Step 2 Establish a Monetization Model
  • Step 3 Make APIs Easy for Developers to Access
  • Step 4 Employ Governance
  • Step 5 Monitor API Use

 

Location:Cloud Spending Spikes, Here’s Where to Invest

  • Excellent distinction by Dave when parsing Cloud’s momentum and investment drivers. “That’s not new money, just moved money.”
  • ” focus on the specific aspects and the value they bring to your business — that’s where you want to align your own investments.”

When DevOps Meets ALM in the Cloud, teams can follow a three step PaaS performance metrics adoption plan:

๏Step 1: Foundational value metrics focus on Time to Market

๏Step 2: Optimization value metrics focus on Portfolio Efficiency

๏Step 3: Transformational value metrics focus on Productivity

 

 

 

 

public cloud, private cloud, and fuzzy cloud demarcation

Public/private and internal/external are two separate dimensions.  Public, private, or community attributes specify how widely the cloud service is shared; a sharing dimension.  Internal or external denote the consumer’s view of the Cloud’s service interface.  The view is associated with a consumer’s responsibility for service development, operations, and management; a responsibility dimension.  A third dimension, on-premise or outsourced, describes where the service assets are located; a location dimension.  Many architects conflate the three dimensions. NIST has recently published a Cloud Computing Reference Architecture which spends considerable prose disentangling the concepts.  According to NIST:

A private cloud gives a single Cloud Consumer organization the exclusive access to and usage of the infrastructure and computational resources. It may be managed either by the Cloud Consumer organization or by a third party, and may be hosted on the organization’s premises (i.e. on-site private clouds) or outsourced to a hosting company (i.e. outsourced private clouds).

 

Let’s run through three quick use cases describing public, private, and community:

Continue reading