Why OpenHub framework?

OpenHub framework is Apache Camel improved for enterprise ... Why not get more?

OpenHub framework is based on matured, well-proofed and very popular integration engine Apache Camel
OpenHub framework extends basic Camel functionality to be more productive and effective in common integration implementation
OpenHub framework is proven and stable solution used in production environments
OpenHub framework is open-source with quality code, covered by many unit tests
OpenHub framework uses database as queue for asynchronous messages processing. Database is well-known technology for most people to administrate or use it. Nevertheless, we want to offer alternative, we want to support JMS as queue.
OpenHub framework is technologically neutral to operation system, application server and database.
OpenHub framework together with application server like Apache Tomcat and database like PostgreSQL represents light-weight ESB solution (server and database can be different)
OpenHub framework uses another well-proven open-source libraries such as Spring Boot, Spring framework, Spring security, Spring Web Services, Hazelcast, Flyway or HttpClient
OpenHub framework offers proven and tested application stack of another dependent libraries and frameworks
OpenHub framework makes use of Spring Boot's style of configuring and creating applications
OpenHub framework can use same tools which can be used by Apache Camel, for example Red Hat® JBoss® Fuse or Hawtio
OpenHub framework has own web administration console

We have many years experience with integration projects, we know common problems, we know how to solve it effectively. OpenHub framework is established on this knowhow.

Main OpenHub framework extensions

OpenHub framework extends Apache Camel in many ways, look at main points:

asynchronous message processing model
- parent-child concept that allows to divide main message into more child messages and process them separately
- obsolete messages checking when messages impact same data
- funnel component is for filtering concurrent messages at specific integration point. This filtering ensures that only one message at one moment will be processed, even in guaranteed order (optional choice).
- guaranteed message processing order
- algorithm is configurable
- synchronous response that input request is saved in queue and asynchronous confirmation with processing result
- monitoring of processing in Admin GUI and via JMX
- alerts define metrics for watching database data and if any metric exceeds its limit then alert is activated and further operation can be executed
- archiving / deleting messages in final state
throttling - functionality that checks count of input requests to integration platform and if this count exceeds defined limit then new requests are restricted
extended error handling with many new Camel events
tracking external systems communication - storing requests and responses
proven application stack
support for Spring Boot's programming style
web administration console
- fully documented REST interface
- searching in asynchronous messages
- message details with requests/responses overview
- manual cancel of next message processing
- restart failed messages
- error codes catalogue
- exposed WSDLs overview
- endpoints overview
extended logging allows to group logs together of one request/message or process
direct call console allows to send custom requests to external system
stopping mode is useful function for correctly OpenHub shutdown
extensions allow to encapsulate new OpenHub framework functionality
support for cluster
- nodes evidence
- clustered scheduled jobs
- clustered memory-grid / cache
flexible external configuration model
running standalone
Java8 support
there is reference implementation