Welcome!

@CloudExpo Authors: Yeshim Deniz, William Schmarzo, Carmen Gonzalez, Pat Romanski, Elizabeth White

Related Topics: @CloudExpo, Microservices Expo, @DevOpsSummit

@CloudExpo: Article

ESBs Are Made for This. Aren’t They? | @CloudExpo #ESB #Cloud #DevOps

The following fictional case study is a composite of actual horror stories I’ve heard over the years

The following fictional case study is a composite of actual horror stories I've heard over the years. Unfortunately, this scenario often occurs when in-house integration teams take on the complexities of DevOps and ALM integration with an enterprise service bus (ESB) or custom integration. It is written from the perspective of an enterprise architect tasked with leading an organization's effort to adopt Agile to become more competitive. The company has turned to Scaled Agile Framework (SAFe) as a way of scaling Agile, since initial attempts at Agile were not successful despite many scrum master training sessions.

I'm told that our SAFe implementation depends on the flow of information between people from different parts of the organization. Because these groups all use different tools, we need to focus on integrating them.

As senior director of Integrated Things for VeryLarge Corp., I have the expertise and know that my team can pull it off. Some of these tools are familiar to my team; we've already connected a couple of them to satisfy one use case, so I feel confident. ESBs are mature and the team is solid. Knowing that we've already deployed ESBawesome successfully makes me feel like this project is in the bag.

So how could I possibly fail? (Spoiler: Here's how):

ESBs Are Made for This
Choosing an ESB for this is easy. I want ESBawesome, since it's got good backing, super adoption and a great community. It has all the "ilities," including high availability, reliability and scalability. Plus it offers fault tolerance, security, tracking and monitoring.

With the tick boxes checked, I can see that ESBawesome already has a connector for some of the systems that we use: Atlassian JIRA and ServiceNow. And because of its API flexibility, ESBawesome can integrate anything. It even offers an easy way to generate connectors!

ESBawesome also fits in well with VeryLarge Corp.'s integration strategy; we've already got it deployed and we have a team built around it.

Team Capacity
The integration team's backlog isn't looking too bad. They're due to come off the current integration project, integrating the inventory-checking module with POS, and should be ready to begin in about six weeks.

Of course, there are a few hiccups. We're having problems with an upgrade of Atlassian's OnDemand JIRA service - where some of JIRAs changes regarding date handling in its REST APIs have caused hundreds of errors in our JIRA - ServiceNow integration. That, and we have to investigate why we've occasionally started seeing "Not authorized to perform action: Invalid key" errors from Rally. Oh, and we're currently blocking an upgrade of IBM RTC from 4.0.1 to 5.0.2 due to some changes and its client libraries from the old version not being compatible with the new version.

On top of that, I'm having multiple problems with the integrations that we've recently created. Not only were the integrations tricky, maintenance is much harder than we thought. These are taking my team more time than anticipated and, as a result, it's looking like a potential multi-month delay before I can even get started on this new integration effort.

Getting Started
It is three months later and we're finally getting started on our first SAFe integration use-case: quality group defect sharing with development. We've got our ESBawesome ESB application building in our CI environment, and we're deploying it continuously to a staging environment. We're operating at 40 percent capacity because the team is still dealing with the RTC upgrade, but we've got a great start in large part because of our previous ESBawesome experience.

To make the integration fault tolerant we've got to be sure to implement the ESBawesome "reliability patterns" correctly. We're using Oracle as a back-end relational database to help with that, but currently we're waiting on IT to set us up with an account with sufficient permissions to create the tables and sequences that we need.

The ESBawesome reliability patterns also call for a proper JMS queue, and we've finally got one going. It's not the same one that we'll use in production, but it's good enough for development. Hopefully things will just work when we switch over.

Connecting the Systems
It turns out that the JIRA connector for ESBawesome isn't all it's cooked up to be. It's definitely not designed for the kinds of use cases that we have in mind. The problem is that the low-level APIs of JIRA (and the connector) don't deal with JIRA issues as a whole - things such as watchers, links and comments are separate API calls.

Our first integration is all about connecting defects from the QA team with the development team. To do that we need the whole JIRA issue to reflect the state of defects filed in HPE ALM. Propagating only some of the state just won't do, so we have to deal with complexity such as a failure to update an issue with links after successfully creating it in JIRA. We're still trying to wrap our heads around how to manage such partially successful state replication.

On the HPE ALM side the ESBawesome connector is coming together slowly. We've had trouble getting the ESBawesome annotation-based REST connector to work for some of HPE ALM's API calls since we've discovered that some of the assumptions about REST APIs aren't holding true for HPE ALM.

Success
It's now four months since we kicked off this project, and the team has caught its first whiff of success. We've got issue creation in JIRA working! We had to hard code some values for some of the required fields in JIRA, but it works!

The next step is to make it easier to add new projects. Our teams in JIRA have all customized their projects with different statuses, fields and severities. I'm surprised at the lack of commonality among our 3,000 JIRA projects.

At the moment, each time we add a new project we have to hard code more values and field-specific logic into our ESBawesome application. The team knows this won't scale, so it has started creating an XML file to configure these settings. With three projects integrated, the XML file is over 4,000 lines. It's going to be tricky editing this file each time we add new projects, but we'd prefer to do that rather than have it hard coded in the application.

"ilities"
The team thinks that it has the fault tolerance and reliability aspects of the integration solved with the Oracle database and JMS.

We want to use ESBawesome's clustering capabilities for scalability and high availability, but we have to adapt some of our application logic to make that work. We chose the wrong level of abstraction for an integration unit of work, and have found that partial failures can result in issues with missing comments and others with duplicated comments, which causes a communication breakdown. Thankfully we haven't deployed into production yet, and it's not affecting any teams directly.

Our initial tests have shown that we don't really need clustering to scale to the levels we'll need with our 20,000+ developers. I'm cringing at the effort that we're spending on this.

We've had to pull in IT again since we'll need a load balancer in front of our ESBawesome cluster to handle transparent fail-over. It looks like they'll be meeting with us sometime next week to talk about environments, hardware allocation and timelines.

Domain Expertise
We've spent so much time trying to get the integration to work, sorting out the details with the technical bits (connectors, environments, databases and everything else) that we haven't had much time to test things with our users. Today we set up a mock trial with the quality group and it turns out that we completely missed something that's essential for this to work.

When an engineer resolves a defect, the quality team doesn't want it to show up as resolved in HPE ALM since they need to design and run tests to verify that it's indeed closed, and create the appropriate regression tests if needed. This only happens for defects in the ‘Ready for Verification' state - but we can't just move defects to that state without a quality engineer verifying that the change made it into a build that's been deployed to the QA environment. We proposed adding a new status, but that didn't fly because it would mess up their reports, so we're working on a way to have the "development status" show up in a new custom field in HPE ALM.

Deployed!
It's eight months since project kick-off and we now have a few "early adopter" teams trying out the new integration.

Initial feedback has been pretty good, but we now have a backlog of over 150 defects and feature requests. Most of them are minor, but a couple of them worry me. I'm not sure how we're going to deal with the loss of HTML formatting in descriptions for example, and HPE ALM's notion of comments as a single large text field is really problematic.

We had to put a few of our other integration projects on hold for awhile to get this one out the door, so we're switching gears right now to get those back on track. The team should be able to get back to this one in a couple of months, at which point we'll look at incorporating feedback from our users. If everything looks good, we'll be bringing on more teams into the trial and hopefully get the green light to deploy department-wide soon.

I'm feeling optimistic, but one of my engineers has given me a heads-up that Atlassian is about to delivery its next version of JIRA. I learned this happens about every six months. How in the world are we going to keep up?

Retrospective
Overall we failed the business. Looking back at what we accomplished, I'm really proud of my team. They overcame a lot of technical issues and really delivered. Unfortunately it wasn't enough.

It took eight months and a big chunk of my integration team's delivery capacity to deliver the first integration. The delay caused us to miss our SAFe implementation goals, and we only delivered a small piece of the integration puzzle. In the meantime, my team was unable to deliver on other projects, which is costing us in lost opportunities.

Here are some of the things we learned along the way:

  • Integrating teams is more complicated than we thought - the technology is only a part of integration. Understanding the reasons why and supporting specific integration use cases of multiple stakeholders is key.
  • This very quickly turned into a large development effort. Thankfully I have a top-notch team, but even they had to overcome some big problems. And there was constant pressure to deliver. VeryLarge Corp. really needed this up and running before we even started, and we simply couldn't deliver fast enough.
  • ESBawesome is a fabulous ESB. It really pulled through for us as a technology platform. The issue for us, though, was that ESB focused on the technical problem. As a result we were in the weeds a lot of the time. For DevOps and ALM/SDLC integration there was a great deal of customization and it was not straightforward. Using an ESB as the basis for our integration meant that we followed an industry-standard integration approach, but it also meant that a lot of software engineering was required. ESBs solve some of the problems, but come with their own complexity, requiring a high degree of expertise.
  • Connectors are a big part of the equation. ESBawesome only came with one of the connectors that we needed, so we ended up building the others ourselves. It's pretty quick to see some initial headway, but it is difficult to get these right. Building a connector means dealing with all of the idiosyncrasies and bugs of a third-party product API, which can vary from one version to the next.
  • The integrations that we built previously take a lot of effort to maintain. Through no fault of our own, APIs are changing and breaking in unexpected ways. This puts a heavy maintenance burden on my team. I'm going to have to plan for even more of this as we proceed with our integration strategy. I'll need to either cut the team's expected delivery of new features, or expand the team to account for maintenance.

It should be obvious that this enterprise architect went into the Agile scaling project unaware of the many technical and business challenges ahead, thereby spending an inordinate amount of time (and money) going down this route. Not till too far down the road did he understand that it can be very costly trying to accomplish this mission using only tools that his company already used. By then, his group had already failed.

More Stories By David Green

David Green is Vice President, Architecture at Tasktop. He was a founding member of MAKE Technologies, where he held the positions of CTO, vice president of technology and principal tools architect. At MAKE, he pioneered a model-driven approach to legacy modernization on the Eclipse platform, integrating business requirements, semantic code generation and data transformation.

David is an Eclipse committer and creator of Mylyn WikiText, a framework and tools for integrating wiki formatting into the Eclipse platform. He is well known for his widely read blog, Green's Opinion, apps for iPhone and Android, and speaking engagements at conferences such as JavaOne and EclipseCon.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@CloudExpo Stories
@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 developm...
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place June 6-8, 2017, at the Javits Center in New York City, New York, is co-located with 20th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry p...
SYS-CON Events announced today that Juniper Networks (NYSE: JNPR), an industry leader in automated, scalable and secure networks, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Juniper Networks challenges the status quo with products, solutions and services that transform the economics of networking. The company co-innovates with customers and partners to deliver automated, scalable and secure network...
SYS-CON Events announced today that Progress, a global leader in application development, has been named “Bronze Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Enterprises today are rapidly adopting the cloud, while continuing to retain business-critical/sensitive data inside the firewall. This is creating two separate data silos – one inside the firewall and the other outside the firewall. Cloud ISVs oft...
Five years ago development was seen as a dead-end career, now it’s anything but – with an explosion in mobile and IoT initiatives increasing the demand for skilled engineers. But apart from having a ready supply of great coders, what constitutes true ‘DevOps Royalty’? It’ll be the ability to craft resilient architectures, supportability, security everywhere across the software lifecycle. In his keynote at @DevOpsSummit at 20th Cloud Expo, Jeffrey Scheaffer, GM and SVP, Continuous Delivery Busine...
As pervasive as cloud technology is -- and as persuasive as the arguments are for using it -- the cloud has its limits. Some companies will always have security concerns about storing data in the cloud and certain high-transaction applications will always be better suited for on-premises storage. Those statements were among the bottom-line takeaways delivered at Cloud Expo this week, a three day, bi-annual event focused on cloud technologies, adoption and associated challenges.
Bert Loomis was a visionary. This general session will highlight how Bert Loomis and people like him inspire us to build great things with small inventions. In their general session at 19th Cloud Expo, Harold Hannon, Architect at IBM Bluemix, and Michael O'Neill, Strategic Business Development at Nvidia, discussed the accelerating pace of AI development and how IBM Cloud and NVIDIA are partnering to bring AI capabilities to "every day," on-demand. They also reviewed two "free infrastructure" pr...
SYS-CON Events announced today that T-Mobile will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. As America's Un-carrier, T-Mobile US, Inc., is redefining the way consumers and businesses buy wireless services through leading product and service innovation. The Company's advanced nationwide 4G LTE network delivers outstanding wireless experiences to 67.4 million customers who are unwilling to compromise on ...
SYS-CON Events announced today that Super Micro Computer, Inc., a global leader in compute, storage and networking technologies, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Supermicro (NASDAQ: SMCI), the leading innovator in high-performance, high-efficiency server technology, is a premier provider of advanced server Building Block Solutions® for Data Center, Cloud Computing, Enterprise IT, Hadoop/...
NHK, Japan Broadcasting, will feature the upcoming @ThingsExpo Silicon Valley in a special 'Internet of Things' and smart technology documentary that will be filmed on the expo floor between November 3 to 5, 2015, in Santa Clara. NHK is the sole public TV network in Japan equivalent to the BBC in the UK and the largest in Asia with many award-winning science and technology programs. Japanese TV is producing a documentary about IoT and Smart technology and will be covering @ThingsExpo Silicon Val...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed 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 at D...
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...
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 ...
“DevOps is really about the business. The business is under pressure today, competitively in the marketplace to respond to the expectations of the customer. The business is driving IT and the problem is that IT isn't responding fast enough," explained Mark Levy, Senior Product Marketing Manager at Serena Software, in this SYS-CON.tv interview at DevOps Summit, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that CollabNet, a global leader in enterprise software development, release automation and DevOps solutions, will be a Bronze Sponsor of SYS-CON's 20th International Cloud Expo®, taking place from June 6-8, 2017, at the Javits Center in New York City, NY. CollabNet offers a broad range of solutions with the mission of helping modern organizations deliver quality software at speed. The company’s latest innovation, the DevOps Lifecycle Manager (DLM), supports Value S...
With billions of sensors deployed worldwide, the amount of machine-generated data will soon exceed what our networks can handle. But consumers and businesses will expect seamless experiences and real-time responsiveness. What does this mean for IoT devices and the infrastructure that supports them? More of the data will need to be handled at - or closer to - the devices themselves.
Building a cross-cloud operational model can be a daunting task. Per-cloud silos are not the answer, but neither is a fully generic abstraction plane that strips out capabilities unique to a particular provider. In his session at 20th Cloud Expo, Chris Wolf, VP & Chief Technology Officer, Global Field & Industry at VMware, will discuss how successful organizations approach cloud operations and management, with insights into where operations should be centralized and when it’s best to decentraliz...
Multiple data types are pouring into IoT deployments. Data is coming in small packages as well as enormous files and data streams of many sizes. Widespread use of mobile devices adds to the total. In this power panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists will look at the tools and environments that are being put to use in IoT deployments, as well as the team skills a modern enterprise IT shop needs to keep things running, get a handle on all this data, and deli...
Grape Up is a software company, specialized in cloud native application development and professional services related to Cloud Foundry PaaS. With five expert teams that operate in various sectors of the market across the USA and Europe, we work with a variety of customers from emerging startups to Fortune 1000 companies.
Financial Technology has become a topic of intense interest throughout the cloud developer and enterprise IT communities. Accordingly, attendees at the upcoming 20th Cloud Expo at the Javits Center in New York, June 6-8, 2017, will find fresh new content in a new track called FinTech.