xocbox ESB

xocbox ESB

a widely adopted enterprise architecture with a “state of the art” container and microservices technology stack

 

An ESB (Enterprise Service Bus) is a software architecture that facilitates the integration of multiple disparate services and systems using a bus (borrowed from electrical engineering) pattern.

The ESB provides a common communication layer between the different systems in order to create a uniformity and manage changes such as new or upgraded services more effectively.

Using an ESB as a lightweight integration backbone reduces “time to market” for new systems (services) and improves organizational agility.

In addition, the ESB provides scalability, extensibility and improved security across applications as it provides a clearly defined barrier between the internal and external systems.

xocbox ESB architecture

xocbox adopted the ESB architecture to accommodate the extensive number of connections and external commercial system integrations,  such as EDI trading partners, service providers (Dropbox, Box) and ecommerce platforms.

The xocbox ESB was developed using a similar technology stack to many of the commercially available ESBs, but is available at a fraction of the licensing cost.

When used in conjunction with (Amazon) AWS it can leverage advanced cloud features such as Auto Scaling in order to handle spikes in traffic and maximize performance.

Technology Stack

  • Karaf – Container

  • Camel – EIP Framework

  • ActiveMQ – Messaging

  • CXF – Web Services

  • Docker & Kubernetes

  • Fabric8 Tooling

  • xocbox Extension Bundles

    1. Federation
    2. Provisioning
    3. Security

Evolve and Change with Business Requirements

xocbox ESB is built on an organic paradigm whereby new modules can evolve and change with business requirements, technology and services. 

ESB modules (pods) comprise of one or more Docker & xocbox extended Karaf microservice containers forming an interconnected virtual federated message bus architecture.

Each module is autonomous but participates based on its respective role and goal within the federation.

Federated Containers

ROLES (TYPE)

1.  Message Broker
2.  State Manager
3.  Registry
4.  Worker
5.  Observer
6.  External Connector
7.  Internal Connector

Federated Containers

GOALS (CONCERNS)

1.  Infrastructure or Business Function based on Role
2.  Maintain Backbone (Interconnected)
3.  High Availability
4.  Security

Backbone

INTEGRATION SERVICES

1.  Publish & Subscribe Messaging
2.  Event Processing
3.  Connectors (Dropbox, Box etc)
4.  Extensible & Scalable
5.  Support for Enterprise Integration Patterns

TO LEARN MORE ABOUT XOCBOX ESB

CALL 858-752-3803

contact xocbox