Welcome!

Microservices Expo Authors: Liz McMillan, Elizabeth White, Carmen Gonzalez, Kalyan Ramanathan, Sematext Blog

Blog Feed Post

Bloomberg Agile Architecture in Action

“We have a mess on our hands,” said John, the CIO of an international hospitality and resort enterprise I’ll call Horizon (I’ve fictionalized the story but it’s based on a combination of true stories). “Every line of business wants something different from IT. There’s lodging, resort operations, restaurant operations, facilities management – even housekeeping, and they all want their own apps.”

It’s a familiar story, of course. I needed to get to the crux of the matter. “Of all the challenges you face, what’s the biggest?” I asked. “What keeps you up at night?”

Hotel graphic“Lack of respect,” John replied. “IT has spent so much time and money over the years before I took this role, just trying to connect everything together and keeping the lights on, that we don’t have any time or money left over to innovate,” he explained. “So now the lines of business feel they have to go around IT and buy apps on their own.”

“Which only makes the problem worse,” I added.

“Precisely.” John ran his fingers through what was left of his hair. “I need to get Horizon out of this Catch-22, where IT’s internal issues prevent us from supporting the business, so the business makes their own technology decisions, which only make our integration, portfolio management, and governance issues worse.”

Time to apply my new approach, the Bloomberg Agile Architecture Technique. The Bloomberg Agile Architecture™ (BAA) Technique offers a way of thinking about and doing architecture that is laser-focused on business agility as the fundamental business driver. Yet while the BAA Technique is an approach to Enterprise Architecture, it’s not a framework or a methodology. In fact, if you’re using TOGAF or SAFe or Zachman or any number of other architectural frameworks or methodologies, the BAA Technique doesn’t require you to throw them out. Rather, the BAA Technique simplifies your choices, as it lays out a particular path through all the options facing the architect that leads to greater business agility. Here’s how it works.

Applying the Bloomberg Agile Architecture Technique within Horizon

The starting point for Horizon’s BAA effort is to cast their problems as business agility drivers. Business agility breaks down into three core priorities: responsiveness and resilience, which are the tactical, reactive drivers, and the strategic, proactive driver of innovativeness. Responsiveness means being able to respond quickly and efficiently to positive change in the business environment, while resilience suggests being able to bounce back from adverse change. Innovativeness, in contrast, means being able to introduce change into the business environment intentionally, in order to achieve strategic benefits like increased market share or penetration of new markets.

At its core, however, BAA is a technology-driven technique, as it provides specific approaches for leveraging modern technologies like Cloud Computing and Big Data Analytics to achieve the business agility goals of the organization. The goal of the architecture exercise, therefore, is to connect the dots between the enterprise agility drivers and the necessary technology changes the IT organization must make in order to achieve those goals.

It’s important to remember, however, that BAA is itself an Agile technique – that is, instead of a heavyweight, big-bang approach, BAA favors an iterative, problem-focused approach that seeks to achieve real progress in a practical, step-by-step manner. As a result, even the most intractable of legacy rats’ nests can benefit from the BAA Technique.

Conversations with Horizon’s line-of-business executives uncovered their agility drivers. They wanted to expand into new markets, improve customer satisfaction in order to increase their repeat customer rate, and add new resort offerings to better compete in existing markets. We worked through these drivers, identifying the core challenges that centered on dealing with change. Numerous challenges presented themselves, and we worked them into their BAA Roadmap (more about such roadmaps in a future Cortex newsletter).

After a few weeks helping them understand their as-is architecture as well as their BAA Roadmap, we settled on a pilot project to serve as the first iteration of their overall BAA deployment. Such pilots serve several purposes: they solve a real, albeit limited problem; they prove the technique works; they get the team up to speed; and they establish an iterative pattern by serving as the first iteration. In the case of Horizon, the pilot focused on their loyalty system.

The loyalty system is supposed to track repeat customers, in order to recognize them as Horizon’s best clientele by offering special promotions, personalized service, and other premiums. Horizon’s problem wasn’t that they didn’t have such a system; their problem was that they had too many loyalty systems. The company had grown internationally through various acquisitions over the years, which led to the addition of various loyalty technologies. On top of these corporate acquisitions, various line-of-business managers within regions had taken it upon themselves to purchase their own loyalty apps. The result was a complicated mess that often didn’t recognize a loyal customer from one geography to the next, as well as causing a variety of related problems, like inconsistent and redundant emails to customers and front desk staff who didn’t know whether someone walking up was a regular or not.

A traditional architectural solution would focus on hammering out the to-be architecture, which in this case might center on a single loyalty system that replaced the motley assortment they started with (which would be unlikely, as every line-of-business manager favors the one they’re using), or more likely an approach to integrating existing systems so that they would present to the customer as a single, coherent application. Such an effort would likely bog down when the data architects tried to rationalize the various and sundry data models that each individual loyalty app depended on. Many months and perhaps millions of dollars later, Horizon might have ended up with a working loyalty system.

That is, until the business environment changed. Perhaps due to a new acquisition. Or maybe an addition of a line of business (there was some buzz about acquiring a cruise line). Or even regulatory change. Now that tightly integrated but fragile loyalty system would no longer meet the requirements, and it would be back to square one.

With BAA, in contrast, there is no to-be architecture – or at least, not in the physical sense of architecting a working app as above. Instead, the focus of the architecture is expecting and supporting ongoing change by specifying technology that is inherently flexible. In other words, architects must begin at the Meta layer, the top layer of the BAA Abstraction Layers diagram below.

 

BAA Abstraction Layers

Bloomberg Agile Architecture Abstraction Layers

 

I discussed the Meta layer in my book, The Agile Architecture Revolution, as well as in other articles over the last few years. At the Meta layer, architects (and others) treat business agility as a metarequirement (a requirement that affects other requirements). The also hammer out metaprocesses (processes for creating and modifying processes) and metapolicies (policies for how to do governance). In the case of Horizon’s loyalty system, work at the Meta level focused on how they will deal with changes that might impact the loyalty system, and what processes and policies at Horizon should be put in place to deal with such change.

While architects must generally start at the Meta level, in practice each iteration should be tackled both top-down and bottom-up at the same time. The architects must have a good understanding of existing technology (working at the Physical layer) as well as the core abstractions that are in place for dealing with that technology (for example, data schemas, Web Service or other API specifications, etc.), which take place at the Abstracted layer. As the team works through the iteration, they will eventually derive recommendations for how to make changes at the Physical and Abstracted layers, but in order to make such recommendations, the architects’ focus must shift to the Dynamic layer.

The Dynamic layer is the key to the entire BAA technique – the glue that ties organizational and process efforts at achieving agility at the Meta layer to the changes Horizon must make to their application and infrastructure environment to support the agility drivers that apply to this iteration. As I explained in the last Cortex newsletter, the focus of the Dynamic layer is on creating abstract models that the underlying infrastructure can resolve at run time into the specific logical representations in the Abstracted layer. Get this step right and you’re on your way to implementing technology that is inherently flexible.

The Intellyx Take

The work so far at Horizon has really just begun, of course. Understanding that abstract models must drive the underlying technology decisions is an important first step, but we must still answer the how question – how to get technology implementations that follow the BAA technique to actually work. I’ll be filling in such important details in my Cortex newsletter as well as my DevX Agile Architecture Revolution blog over time. (If you can’t wait, then join me in one of my upcoming Bloomberg Agile Architecture Certification courses or drop me a line.)

In the meantime, take another look at the BAA Abstraction Layers diagram above – especially if you’re an architect with years of experience dealing with other, similar layer cake diagrams. True, the bottom two layers are tried and true – nothing particularly new there. To really understand why BAA is different, you must understand the top two layers: in and of themselves, and how they relate to everything else. Simply adding one layer of abstraction on top of another is also a familiar architectural rat hole, but one I’ve been careful to avoid. If you understand why that is, you’re on your way to understanding Bloomberg Agile Architecture – just as John at Horizon is well on his way to getting some respect.

Horizon is a fictitious company. Any similarity to a real company is purely coincidental. Image credit: Kevin Dooley

Read the original blog entry...

More Stories By Jason Bloomberg

Jason Bloomberg is the leading expert on architecting agility for the enterprise. As president of Intellyx, Mr. Bloomberg brings his years of thought leadership in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture to a global clientele of business executives, architects, software vendors, and Cloud service providers looking to achieve technology-enabled business agility across their organizations and for their customers. His latest book, The Agile Architecture Revolution (John Wiley & Sons, 2013), sets the stage for Mr. Bloomberg’s groundbreaking Agile Architecture vision.

Mr. Bloomberg is perhaps best known for his twelve years at ZapThink, where he created and delivered the Licensed ZapThink Architect (LZA) SOA course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in 2011. He now runs the successor to the LZA program, the Bloomberg Agile Architecture Course, around the world.

Mr. Bloomberg is a frequent conference speaker and prolific writer. He has published over 500 articles, spoken at over 300 conferences, Webinars, and other events, and has been quoted in the press over 1,400 times as the leading expert on agile approaches to architecture in the enterprise.

Mr. Bloomberg’s previous book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation. He also co-authored the books XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996).

Prior to ZapThink, Mr. Bloomberg built a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting).

@MicroservicesExpo Stories
Between 2005 and 2020, data volumes will grow by a factor of 300 – enough data to stack CDs from the earth to the moon 162 times. This has come to be known as the ‘big data’ phenomenon. Unfortunately, traditional approaches to handling, storing and analyzing data aren’t adequate at this scale: they’re too costly, slow and physically cumbersome to keep up. Fortunately, in response a new breed of technology has emerged that is cheaper, faster and more scalable. Yet, in meeting these new needs they...
@DevOpsSummit taking place June 6-8, 2017 at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @DevOpsSummit at Cloud Expo New York Call for Papers is now open.
Logs are continuous digital records of events generated by all components of your software stack – and they’re everywhere – your networks, servers, applications, containers and cloud infrastructure just to name a few. The data logs provide are like an X-ray for your IT infrastructure. Without logs, this lack of visibility creates operational challenges for managing modern applications that drive today’s digital businesses.
Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more business becomes digital the more stakeholders are interested in this data including how it relates to business. Some of these people have never used a monitoring tool before. They have a question on their mind like “How is my application doing” but no id...
Information technology is an industry that has always experienced change, and the dramatic change sweeping across the industry today could not be truthfully described as the first time we've seen such widespread change impacting customer investments. However, the rate of the change, and the potential outcomes from today's digital transformation has the distinct potential to separate the industry into two camps: Organizations that see the change coming, embrace it, and successful leverage it; and...
In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals – as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.
Monitoring of Docker environments is challenging. Why? Because each container typically runs a single process, has its own environment, utilizes virtual networks, or has various methods of managing storage. Traditional monitoring solutions take metrics from each server and applications they run. These servers and applications running on them are typically very static, with very long uptimes. Docker deployments are different: a set of containers may run many applications, all sharing the resource...
Keeping pace with advancements in software delivery processes and tooling is taxing even for the most proficient organizations. Point tools, platforms, open source and the increasing adoption of private and public cloud services requires strong engineering rigor – all in the face of developer demands to use the tools of choice. As Agile has settled in as a mainstream practice, now DevOps has emerged as the next wave to improve software delivery speed and output. To make DevOps work, organization...
Join Impiger for their featured webinar: ‘Cloud Computing: A Roadmap to Modern Software Delivery’ on November 10, 2016, at 12:00 pm CST. Very few companies have not experienced some impact to their IT delivery due to the evolution of cloud computing. This webinar is not about deciding whether you should entertain moving some or all of your IT to the cloud, but rather, a detailed look under the hood to help IT professionals understand how cloud adoption has evolved and what trends will impact th...
Internet of @ThingsExpo, taking place June 6-8, 2017 at the Javits Center in New York City, New York, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @ThingsExpo New York Call for Papers is now open.
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his session at @DevOpsSummit 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, showed how customers are able to achieve a level of transparency that enables everyone fro...
You have great SaaS business app ideas. You want to turn your idea quickly into a functional and engaging proof of concept. You need to be able to modify it to meet customers' needs, and you need to deliver a complete and secure SaaS application. How could you achieve all the above and yet avoid unforeseen IT requirements that add unnecessary cost and complexity? You also want your app to be responsive in any device at any time. In his session at 19th Cloud Expo, Mark Allen, General Manager of...
The 20th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held June 6-8, 2017, at the Javits Center in New York City, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit your speaking proposal ...
"Dice has been around for the last 20 years. We have been helping tech professionals find new jobs and career opportunities," explained Manish Dixit, VP of Product and Engineering at Dice, in this SYS-CON.tv interview at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Rapid innovation, changing business landscapes, and new IT demands force businesses to make changes quickly. In the eyes of many, containers are at the brink of becoming a pervasive technology in enterprise IT to accelerate application delivery. In this presentation, attendees learned about the: The transformation of IT to a DevOps, microservices, and container-based architecture What are containers and how DevOps practices can operate in a container-based environment A demonstration of how ...
As we enter the final week before the 19th International Cloud Expo | @ThingsExpo in Santa Clara, CA, it's time for me to reflect on six big topics that will be important during the show. Hybrid Cloud This general-purpose term seems to provide a comfort zone for many enterprise IT managers. It sounds reassuring to be able to work with one of the major public-cloud providers like AWS or Microsoft Azure while still maintaining an on-site presence.
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Phil Hombledal, Solution Architect at CollabNet, discussed how customers are able to achieve a level of transparency that e...
In his session at 19th Cloud Expo, Claude Remillard, Principal Program Manager in Developer Division at Microsoft, contrasted how his team used config as code and immutable patterns for continuous delivery of microservices and apps to the cloud. He showed how the immutable patterns helps developers do away with most of the complexity of config as code-enabling scenarios such as rollback, zero downtime upgrades with far greater simplicity. He also demoed building immutable pipelines in the cloud ...
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long develop...
Get deep visibility into the performance of your databases and expert advice for performance optimization and tuning. You can't get application performance without database performance. Give everyone on the team a comprehensive view of how every aspect of the system affects performance across SQL database operations, host server and OS, virtualization resources and storage I/O. Quickly find bottlenecks and troubleshoot complex problems.