All posts by haddadcblg

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

Big Data Blocking and Tackling

Are you practicing Big data blocking and tackling actions?   Ron Bodkin (@ronbodkin) penned a good post describing the value of having information in one place; the mantra of data warehouses and data marts.

While Hadoop makes it easier to warehouse data (due to flexible schema model), effective analytics across disparate data sources still requires defining data semantics, data mapping, and master data sources. Don’t forget these important foundational building blocks.

Continue reading

soccer field

Tracking Soccer Game Play with Big Data Streaming, Internet of Things, and Complex Event Processing

Teams gain a competitive edge by analyzing Big Data streams. By using complex event processing and MapReduce based technologies, teams can improve performance. By establishing a feedback loop, your team can visualize business activity, understand impact, and take positive actions.

 

Big data Life Cycle

One powerful Big Data streaming example, soccer match activity data captured by embedded sensors were streamed and analyzed to understand how player actions impact soccer play.

Continue reading

DevOps Days

DevOps Equals DevOps Principles Plus DevOps Practices

Successful, long-lasting movement have 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.

DevOps Principles

DevOps value is derived in the core principles that started the movement:

  • Iterative
  • Incremental
  • Continuous
  • Automated
  • Self-service
  • Collaborative
  • Holistic

Teams should analyze existing processes against the principles, and see where DevOps practices can add value.

 

DevOps Practices

A few identified DevOps practices include:

  • Self-service configuration
  • Automated provisioning
  • Continuous build
  • Continuous integration
  • Continuous delivery
  • Automated release management
  • Incremental testing

DevOps Tool Capabilities

As Mike (@madgreek65) and Abel (G+AbelAvram) mention, teams commonly focus on tools instead of value. DevOps friendly tooling delivers:

  • Self service project via project configuration portals
  • Policy configuration for Security, service levels, frameworks, usage, topology concerns
  • Automated platform provisioning via service tier templates, frameworks, and policy enforcement points (PEP)
  • Process automation with Continuous build, test, and deployment. Code promotion and synchronization across environments and servers
  • Dependency analysis and impact analysis

DevOps Value

For value metrics, break up DevOps goals into foundational, optimal, and transformational categories. For example,

Foundation

  • Time and effort to create new application environment
  • Time to redeploy application
  • Time to promote application into a new lifecycle phase

Optimize

  • Dynamically right-size infrastructure scale
  • Re-use existing platform services and business services from resource pool instead of re-building solution stack

Transformation

  • Time and effort required integrating business process, event processor – creating a complex app.
  • Time and effort required to apply policy across tenant(s)
  • Cost to operate application per user or transaction

 

Keep a DevOps Focus

So look beyond adding the cool ‘DevOps Engineer’ title and tool names (i.e. Puppet, Chef, Ansible, and Salt) onto your resume.   DevOps is about principles, practices, and creating a collaborative environment that improves software delivery and increases business value.   With good information readily available on the Web, and conference series (for example, DevOpDays ) focused on core DevOps principles and practices, you can stay tuned into the DevOps way of thinking!

DevOps Days

Feature Image Courtesy of DevOpsDays.org

Reducing Cloud Computing Cost

Warning: Cloud projects may cost more than terrestrial projects. Cloud projects may not reduce IT cost.    Unless, you carefully consider appropriate Cloud usage scenarios, build Cloud-aware solutions, and choose Cloud-native platforms.

Jared Wray (@jaredwray) has obviously been thinking about Cloud’s value proposition, market awareness, and end-user adoption scenarios. Jared has penned an excellent post on Cloud computings hidden costs that delivers in-depth analysis on Cloud computing dynamics.

Many news writers have documented cloud’s hidden cost, for example Beth Pariseau (@pariseauTT) at SeachCloudCOmputing documenting cloud sticker shock.    Beth outlines a key areas to watch:

  • Server instance performance
  • Provisioning cost
  • Data storage cost
  • Distaster recovery,  monitoring, and network bandwidth

Why Be Concerned About Cloud Cost?

Archana Venkatraman (@archanatweets) posts in ComputerWeekly that a

global survey of CIOs into attitudes and concerns relating to cloud computing has revealed that almost 80% are concerned about the hidden costs associated with cloud computing.

Adding to the conversation, Joe Mckendrick (@joemckendrick) details specific points of concern:

  • Poor end user experience due to performance bottlenecks (64 percent). This goes right to the customer end-user experience as well, since e-commerce is the leading cloud application area, the survey finds  – 78 percent of respondents are already using cloud resources to support e-commerce.
  • The impact of poor performance on brand perception and customer loyalty (51 percent).
  • Loss of revenue due to poor availability, performance, or troubleshooting cloud services (44 percent).
  • Increased costs of resolving problems in a more complex environment (35 percent).
  • Increased effort required to manage vendors and service level agreements (23 percent).

Correlating hidden cost fears,  IBM’s recent admission that  Cloud Foundry demand is “in its infancy” (reported by Joe Curtis  @JoeCurtis_CBR), and a 2013 summer story of lagging Enterprise PaaS adoption, many  IT professionals may predict that

PaaS may be poised to enter the trough of disillusionment.

The Smart Cloud Path Forward

Fortunately, smart tech leaders are presenting a viable path forward.  A path that jumps over the disillusionment gulf.  I especially appreciate Jared’s statement,

most savings come when users take advantage of the platform to optimize their workloads. 

When workloads and the platform may become Cloud-aware, Cloud solutions can live up to the hype.  Successful teams optimize code, configuration, and policy to capitalize on Cloud-native architecture and capabilities.   Rather than a ‘Bigger in Texas’ design mentality, a frugal, just-enough at the right time, design must pervade the Cloud solution.   I would like to see the industry move towards benchmarking how multi-tenant design effects ‘tenant density’ (tenant count divided by granularity), scaling time lag, and solution cost.

Reducing Cloud Computing Cost: Recommended Reading

PaaS TCO and PaaS ROI: hared multi-tenant container PaaS 

Building Multi-Tenant SaaS Applications 

Cloud-Native PaaS Architecture

Hidden Cost of Cloud Computing  (Joe Mckendrick)

Where is the Rub: Cloud Computings Hidden Costs (Jared Wray)

 

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

 

 

 

 

Reshape Reference Architecture: Why, What, How

The reference architectures of the past (i.e. client-server, web application, SOA services) are not adequately addressing current business demand, use cases, and expectations.  IT must update  reference architecture models to remain relevant and effective.

Often outdated processes, tools, and skills inhibit IT’s ability to be a strategic enabler and gain an IT business edge.  By adopting a new, Responsive IT delivery model based on an updated reference architecture, teams can foster effective business collaboration, responsive iterations, streamlined processes, and no wait states; enabling business to operate at the speed of now.

What reference architecture goal-state is required to meet business demands and expectations?

A reference architecture should enable internal and external business service consumers, address future IT strategies, and transition current IT infrastructure and team skill sets.   Do you have a seven step plan describing how to reshape your reference architecture?

A three part slideshare series outlines why reshape reference architecture, what reference architecture models make sense today, and how to reshape reference architecture.

Continue reading

Governance

Defining a SOA governance approach

Service Oriented Architecture initiative success requires creating loosely coupled consumer-provider connections, enforcing a separation of concerns between consumer and provider, exposing a set of re-usable, shared services, and gaining service consumer adoption. Many teams find a SOA or REST focus may not improve IT agility, but result in simply swapping out IT toolsets, message formats, and protocols.

SOA Governance mitigates risk in failing to deliver the [A] in SOA.

Continue reading

Integrated Business

How to build an integrated business

Obtaining a well integrated business is a core connected business tenet. By integrating business data, processes, rules, services and capabilities between internal and external IT assets, IT teams create an environment accelerating business interactions inside, outside, and across organizational boundaries.   Business interaction acceleration leads to increased revenue growth and enhanced customer satisfaction.

Continue reading