Microservices Expo Authors: Roger Strukhoff, Don MacVittie, Liz McMillan, Elizabeth White, Pat Romanski

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
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.
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
In his general session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, discussed cloud as a ‘better data center’ and how it adds new capacity (faster) and improves application availability (redundancy). The cloud is a ‘Dynamic Tool for Dynamic Apps’ and resource allocation is an integral part of your application architecture, so use only the resources you need and allocate /de-allocate resources on the fly.
For those unfamiliar, as a developer working in marketing for an infrastructure automation company, I have tried to clarify the different versions of DevOps by capitalizing the part that benefits in a given DevOps scenario. In this case we’re talking about operations improvements. While devs – particularly those involved in automation or DevOps will find it interesting, it really talks to growing issues Operations are finding. The problem is right in front of us, we’re confronting it every day,...
SYS-CON Events announced today that SoftNet Solutions will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. SoftNet Solutions specializes in Enterprise Solutions for Hadoop and Big Data. It offers customers the most open, robust, and value-conscious portfolio of solutions, services, and tools for the shortest route to success with Big Data. The unique differentiator is the ability to architect and ...
The general concepts of DevOps have played a central role advancing the modern software delivery industry. With the library of DevOps best practices, tips and guides expanding quickly, it can be difficult to track down the best and most accurate resources and information. In order to help the software development community, and to further our own learning, we reached out to leading industry analysts and asked them about an increasingly popular tenet of a DevOps transformation: collaboration.
Application transformation and DevOps practices are two sides of the same coin. Enterprises that want to capture value faster, need to deliver value faster – time value of money principle. To do that enterprises need to build cloud-native apps as microservices by empowering teams to build, ship, and run in production. In his session at @DevOpsSummit at 19th Cloud Expo, Neil Gehani, senior product manager at HPE, will discuss what every business should plan for how to structure their teams to d...
When we talk about the impact of BYOD and BYOA and the Internet of Things, we often focus on the impact on data center architectures. That's because there will be an increasing need for authentication, for access control, for security, for application delivery as the number of potential endpoints (clients, devices, things) increases. That means scale in the data center. What we gloss over, what we skip, is that before any of these "things" ever makes a request to access an application it had to...
The best way to leverage your Cloud Expo presence as a sponsor and exhibitor is to plan your news announcements around our events. The press covering Cloud Expo and @ThingsExpo will have access to these releases and will amplify your news announcements. More than two dozen Cloud companies either set deals at our shows or have announced their mergers and acquisitions at Cloud Expo. Product announcements during our show provide your company with the most reach through our targeted audiences.
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, will discuss how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team a...
Virgil consists of an open-source encryption library, which implements Cryptographic Message Syntax (CMS) and Elliptic Curve Integrated Encryption Scheme (ECIES) (including RSA schema), a Key Management API, and a cloud-based Key Management Service (Virgil Keys). The Virgil Keys Service consists of a public key service and a private key escrow service. 

More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes ho...
Digitization is driving a fundamental change in society that is transforming the way businesses work with their customers, their supply chains and their people. Digital transformation leverages DevOps best practices, such as Agile Parallel Development, Continuous Delivery and Agile Operations to capitalize on opportunities and create competitive differentiation in the application economy. However, information security has been notably absent from the DevOps movement. Speed doesn’t have to negat...
SYS-CON Events announced today that eCube Systems, the leading provider of modern development tools and best practices for Continuous Integration on OpenVMS, will exhibit at SYS-CON's @DevOpsSummit at Cloud Expo New York, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. eCube Systems offers a family of middleware products and development tools that maximize return on technology investment by leveraging existing technical equity to meet evolving business needs. ...
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...
Whether they’re located in a public, private, or hybrid cloud environment, cloud technologies are constantly evolving. While the innovation is exciting, the end mission of delivering business value and rapidly producing incremental product features is paramount. In his session at @DevOpsSummit at 19th Cloud Expo, Kiran Chitturi, CTO Architect at Sungard AS, will discuss DevOps culture, its evolution of frameworks and technologies, and how it is achieving maturity. He will also cover various st...
operations aren’t merging to become one discipline. Nor is operations simply going away. Rather, DevOps is leading software development and operations – together with other practices such as security – to collaborate and coexist with less overhead and conflict than in the past. In his session at @DevOpsSummit at 19th Cloud Expo, Gordon Haff, Red Hat Technology Evangelist, will discuss what modern operational practices look like in a world in which applications are more loosely coupled, are deve...
19th Cloud Expo, taking place November 1-3, 2016, 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. Meanwhile, 94% of enterpri...
DevOps is speeding towards the IT world like a freight train and the hype around it is deafening. There is no reason to be afraid of this change as it is the natural reaction to the agile movement that revolutionized development just a few years ago. By definition, DevOps is the natural alignment of IT performance to business profitability. The relevance of this has yet to be quantified but it has been suggested that the route to the CEO’s chair will come from the IT leaders that successfully ma...
As the world moves toward more DevOps and Microservices, application deployment to the cloud ought to become a lot simpler. The Microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. Serverless computing is revolutionizing computing. In his session at 19th Cloud Expo, Raghav...