Welcome!

Microservices Expo Authors: Flint Brenton, Elizabeth White, Pat Romanski, Cameron Van Orman, Jason Bloomberg

Related Topics: Microservices Expo, Java IoT, Linux Containers, @CloudExpo

Microservices Expo: Article

Bloomberg Agile Architecture in Action

How to think about and do architecture laser-focused on business agility as the fundamental business driver

“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?”

“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.

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

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
The nature of the technology business is forward-thinking. It focuses on the future and what’s coming next. Innovations and creativity in our world of software development strive to improve the status quo and increase customer satisfaction through speed and increased connectivity. Yet, while it's exciting to see enterprises embrace new ways of thinking and advance their processes with cutting edge technology, it rarely happens rapidly or even simultaneously across all industries.
Is advanced scheduling in Kubernetes achievable? Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, will answer these questions and demonstrate techniques for implementing advanced scheduling. For example, using spot instances ...
With the rise of DevOps, containers are at the brink of becoming a pervasive technology in Enterprise IT to accelerate application delivery for the business. When it comes to adopting containers in the enterprise, security is the highest adoption barrier. Is your organization ready to address the security risks with containers for your DevOps environment? In his session at @DevOpsSummit at 21st Cloud Expo, Chris Van Tuin, Chief Technologist, NA West at Red Hat, will discuss: The top security r...
DevSecOps – a trend around transformation in process, people and technology – is about breaking down silos and waste along the software development lifecycle and using agile methodologies, automation and insights to help get apps to market faster. This leads to higher quality apps, greater trust in organizations, less organizational friction, and ultimately a five-star customer experience. These apps are the new competitive currency in this digital economy and they’re powered by data. Without ...
With the modern notion of digital transformation, enterprises are chipping away at the fundamental organizational and operational structures that have been with us since the nineteenth century or earlier. One remarkable casualty: the business process. Business processes have become so ingrained in how we envision large organizations operating and the roles people play within them that relegating them to the scrap heap is almost unimaginable, and unquestionably transformative. In the Digital ...
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
Today most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes significant work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reducti...
Most of the time there is a lot of work involved to move to the cloud, and most of that isn't really related to AWS or Azure or Google Cloud. Before we talk about public cloud vendors and DevOps tools, there are usually several technical and non-technical challenges that are connected to it and that every company needs to solve to move to the cloud. In his session at 21st Cloud Expo, Stefano Bellasio, CEO and founder of Cloud Academy Inc., will discuss what the tools, disciplines, and cultural...
Enterprises are moving to the cloud faster than most of us in security expected. CIOs are going from 0 to 100 in cloud adoption and leaving security teams in the dust. Once cloud is part of an enterprise stack, it’s unclear who has responsibility for the protection of applications, services, and data. When cloud breaches occur, whether active compromise or a publicly accessible database, the blame must fall on both service providers and users. In his session at 21st Cloud Expo, Ben Johnson, C...
21st International Cloud Expo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Me...
‘Trend’ is a pretty common business term, but its definition tends to vary by industry. In performance monitoring, trend, or trend shift, is a key metric that is used to indicate change. Change is inevitable. Today’s websites must frequently update and change to keep up with competition and attract new users, but such changes can have a negative impact on the user experience if not managed properly. The dynamic nature of the Internet makes it necessary to constantly monitor different metrics. O...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
There is a huge demand for responsive, real-time mobile and web experiences, but current architectural patterns do not easily accommodate applications that respond to events in real time. Common solutions using message queues or HTTP long-polling quickly lead to resiliency, scalability and development velocity challenges. In his session at 21st Cloud Expo, Ryland Degnan, a Senior Software Engineer on the Netflix Edge Platform team, will discuss how by leveraging a reactive stream-based protocol,...
Many organizations adopt DevOps to reduce cycle times and deliver software faster; some take on DevOps to drive higher quality and better end-user experience; others look to DevOps for a clearer line-of-sight to customers to drive better business impacts. In truth, these three foundations go together. In this power panel at @DevOpsSummit 21st Cloud Expo, moderated by DevOps Conference Co-Chair Andi Mann, industry experts will discuss how leading organizations build application success from all...
The last two years has seen discussions about cloud computing evolve from the public / private / hybrid split to the reality that most enterprises will be creating a complex, multi-cloud strategy. Companies are wary of committing all of their resources to a single cloud, and instead are choosing to spread the risk – and the benefits – of cloud computing across multiple providers and internal infrastructures, as they follow their business needs. Will this approach be successful? How large is the ...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
One of the biggest challenges with adopting a DevOps mentality is: new applications are easily adapted to cloud-native, microservice-based, or containerized architectures - they can be built for them - but old applications need complex refactoring. On the other hand, these new technologies can require relearning or adapting new, oftentimes more complex, methodologies and tools to be ready for production. In his general session at @DevOpsSummit at 20th Cloud Expo, Chris Brown, Solutions Marketi...