Enterprise Service Bus (ESB)
DivIHN has particular technical knowledge and experience in the deployment of Enterprise Service Bus technologies. Sometimes thought of as middleware, message managers, or data brokers, in SOA implementations, the selection, installation, and configuration of an ESB and its connections with internal and external business systems is the most important, foundational technical component of the new ecosystem.
The ESB is a platform-agnostic architectural pattern representing a basic set of functional requirements used to enable and manage application-to-application (inter-process) communication across an enterprise, typically providing mediation, transformation, routing, and other functions through a stack of services which insulate applications from direct contact with each other.
DivIHN has experience with both commercial and open source ESB technologies. Although broadly similar in function and purpose, conceptualization of the deployment strategy of these technologies in the unique ecosystem of a given enterprise begins with a reference architecture. As new enterprise services are added to the environment, new connectors, interfaces and data flows are added to the applied architecture.
Data mapping, normalization and transformation, schema translation and mediation are some of the data-centric services which often reside in the ESB or are closely bound to it. DivIHN’s ESB experts are not only adept at configuring the ESB “plumbing” but also in the enabling these data-centric services.
E-business, connected business, SAAS, cloud, and hybrid cloud are just some of the short names for a wide variety of technology trends and initiatives that continue to transform the way IT happens. Organizations are increasingly required to build and operate their IT ecosystem strategies as interconnected on-premises and off-premises services. As a best practice interconnected services are orchestrated within an architectural pattern known as Service Oriented Architecture. DivIHN’s experienced advisors understand the potential opportunities and challenges of designing and deploying a Service Oriented Architecture to position your information systems for growth and flexibility.
Implementation of a Service Oriented Architecture (SOA) is much more than a technology initiative. Very often, business drivers, such as a new trading partnership or adoption of a new cloud-based business technology solution suggest implementation of a Service Oriented Architecture to enable orchestrated, secure, and reliable messaging between business systems and platforms. DivIHN’s Business Analysts and Architects will help you translate the business requirements and drivers into technology requirements and imperatives to guide your SOA implementation.
Successful implementation of a Service Oriented Architecture (SOA) depends on clear understanding of the business processes to be enabled by the SOA technology. At times, an organization must first undertake an assessment of the current state business processes potentially involved in the SOA initiative and reengineer those business processes to take advantage of the interconnected services provided by internal and external systems.
There are specific technologies and technical disciplines involved in the deployment of an SOA solution. These include core middleware “orchestration” technologies, connectivity components for each service to be integrated, and supporting technologies such as security services and more. DivIHN’s SOA architects and engineers have experience in deploying these technologies in wide variety of enterprises and disparate technology landscapes.
The DivIHN-recommended SOA End State is often described in the format of Blueprints. Blueprints are high-level visual representations of the tangible components of the SOA End State Architecture. There may be one Blueprint reflecting an end-state or several reflecting transitional application and data architectures.
A roadmap is a key deliverable in planning the implementation of a Service Oriented Architecture. It allows IT and the businesses to define one or more phases in the transition from the current non-integrated environment to an integrated service-oriented environment. The roadmap goes hand in hand with transitional and end-state architectures, describing the timing and major dependencies for each transition.