While some organizations have been very successful in their integration development efforts, others have struggled.
Message flows that could be developed in time frames of hours to days are instead developed in time frames of weeks to months.
Additionally, many of the developed “integrations” actually look more like small applications than discrete services.
This type of design serves the near-term business owner needs but fails to leverage the developed integrations, it also fails to meet the organizations longer-term SOA goals.
This latter is a high, but hidden, cost.
The TxMQ Integration Store can solve this problem!
Why use TxMQ's Integration Store?
All of these engineers were part of the vendor teams that initially developed and deployed these software technologies.
Each of our developers have over two decades of integration experience.
It was their combined experience, and their recognition of the solution similarities across customers and Lines of Business, that developed the TxMQ Integration Store.
What makes TxMQ the best choice?
TxMQ’s On Demand Integration Services are a logical extension of the industry Best Practices.
Rather than developing an internal “Center of Excellence”, use an external one; ours!
Our developers represent the best in the business and specialize in developing integration solutions.
You can leverage this capability “On Demand”, without having to pay any costs for leaving these elite developers idle.
Rapid Time to Market
Integrate in a matter of days instead of months
Decreased Total Cost of Ownership
Significantly lower your TCO
Enhance Future In-House Development
Provided integrations serve as model templates for future in-house dev
Middleware software is now a very sophisticated and mature solution.
This is especially true for the Messaging engines (e.g. IBM MQ) and Message Brokers (e.g. IBM IIB), which started the middleware revolution. The industry now has several decades of experience in building and deploying integration software using these technologies. As a result, a substantial catalog of both “Best” and “Worst” practices have been developed.
Furthermore, common patterns across multiple organizations and Lines of Business have been recognized.
One result of the evolution and globalization of the modern IT workforce has been accelerated career arcs and correspondingly lowered experience levels.
What do you mean?
- The first consequence is that many of the developers in this space have not had the opportunity to see the historical arc of these solutions.
- The second consequence is that a large percentage of the developers are not Subject Matter Experts, but are instead much more junior.
The overall result is that the “wheel” continues to become re-invented and the same lessons continue to be re-learned (or worse, ignored).
These workforce changes have had a particularly negative impact in the area of integration software development. All of the integration technologies have a much longer learning curve than standard software development; for example Java. Integration development requires a knowledge of multiple domains (programming, data modeling, database, testing, etc.). The programming itself spans multiple languages (Native Toolkit nodes, ESQL, SQL, Java .Net, XPath, etc.). A plethora of standards and protocols are involved in integration (Legacy data, DFDL, XML, XSD, MIME, HTTP, SOAP, REST, SQL, XPath, etc.) Since integration often spans multiple platforms (Windows, UNIX, mainframe, etc.), significant platform and debugging skills are required.
The industry Best Practice for integration development has been to establish a “Center of Excellence” approach.
What is the Center of Excellence approach?
The resources in the “Center” specialize in developing integration solutions and are led by Subject Matter Experts.
This allows junior resources to accelerate their skill acquisition and leverages the knowledge of the SMEs.
The “Center” also allows for the development of standards and reusable solutions.
The result of the challenges described is that many organizations have struggled to achieve excellence in their integration software development.
A number of factors have contributed to this approach.
- Organizational challenges sometimes prevent “Centers of Excellence” from being developed. Organizational change is a well-known hurdle in the SOA maturity process.
- The shortage of true Subject Matter Experts to lead integration development has also been a problem.
- The longer learning curve associated with integration development has exacerbated the problem.
- The shortage of highly skilled Enterprise Architects has contributed to a “programming” rather than a “services” design paradigm
- DevOps and Agile approaches, as implemented in many organizations, have tended to focus on programming rather than design. This is not a methodological fault, but more an issue of what can be easily measured. Design quality is notoriously difficult to measure.