Neuron ESB is an Enterprise Service Bus (ESB) which provides an application integration and web service platform built entirely on Microsoft .NET. While specific definitions of ESB’s vary, there is consistent agreement within the industry as to the types of capabilities an ESB should provide; Neuron ESB provides all of these, and more.
Neuron ESB provides the following:
- Message routing (content based, static, rules based)
- Mediation (protocol bridging, LOB adapters)
- Message processing (transformation, enhancement/augmentation)
- Management (auditing, monitoring,, logging)
- Quality of Service (security, delivery reliability, transactions)
Neuron ESB provides both stateless and state-full services giving developers the ability to control performance over durability. It provides a middleware topic-based messaging layer that isolates and decouples communicating parties (services or applications), allowing them to effectively exchange messages. When using Neuron ESB, applications and/or services simply publish messages onto the bus, without regard to the type or number of consumers; similarly, they may subscribe to specific messages or groups of messages, without regard to the source of the messages. This frees the developers from spending time on messaging business logic and allows them to concentrate on the specific business logic associated with manipulating the message data.
Developing solutions using Neuron ESB is straightforward, familiar, and consistent with existing .NET development processes and tools. Neuron ESB developer extensions to Visual Studio allow developers to seamlessly combine their Web services and application development with Neuron configuration elements and code snippets.
Neuron ESB lowers your TCO by helping you quickly realize a variety of important benefits without the need for rare and expensive expertise required of competing ESB vendors. For example, Neuron ESB can help you:
- Quickly integrate your systems and applications
- Insert/retrieve data from database such as SQL Server, Oracle, and DB2 with zero coding
- Interconnect heterogeneous systems, legacy applications, and the newest technologies with no coding
- Leverage your existing assets
- Utilize current .NET developer skills. No retraining, or special tools required
- Use .NET and WCF adapters to connect to your applications and systems
- Easily extend your applications
- Add workflow with no coding
- Add business processes, with rules, transformation, logic, etc., with no coding
- Gain visibility into your business
- Extract basic information from messages for business indicators
- Populate data warehouses, and analysis stores in real time
- Create a powerful, reusable infrastructure
- Common code is in the ESB, not applications
- IT resources can manage infrastructure with no impact to applications/services
- Evolves with you, and in support of your objectives
- Get monitoring, management, admin for “free”
- Utilize industry standards
How Does Neuron ESB Work?
Neuron ESB provides a middleware messaging layer that isolates and decouples communicating parties (services or applications), allowing them to effectively exchange messages. When using Neuron ESB, applications and/or services simply publish messages onto the bus, without regard to the type or number of consumers; similarly, they may subscribe to specific messages or groups of messages, without regard to the source of the messages. This frees the developers from spending time on messaging business logic and allows them to concentrate on the specific business logic associated with manipulating the message data.
The following diagram depicts a fictional Neuron ESB configuration illustrating interconnections in a heterogeneous environment, as well as the major Neuron ESB functional components.
Neuron ESB is built on top of the .NET Framework and fully leverages WCF, WF, and other framework components, using an open architecture that embraces extensibility. Users can develop custom adapters, messaging processing, business processes(stateless workflow), and system level services to extend the out-of-the box functionality while maintaining consistent tooling and operational characteristics. While support of the Microsoft stack is very strong, interoperability with other vendor platforms is broad and far reaching due to Neuron’s adoption of the most common messaging standards and specifications. Some of the features that Neuron ESB provides are:
- XCopy/Incremental/Command Line deployment
- Hierarchical Topic based Pub/Sub Messaging
- Real time, in memory Messaging
- Guaranteed/Durable Messaging
- Event-based distributable .NET client AP
- Centrally Managed/Distributed Execution
- Adapters and Adapter Framework
- In memory Service Broker (SOAP/REST)
- Monitoring/Dashboard/Performance Counters
- Microsoft Azure Support
- Real Time Business Process workflow designer
- Ability to create custom Process steps
- Event-based plug-ins for Dynamics CRM, Excel and SharePoint
Neuron ESB is unique in the industry in that it allows the user to specify the transport protocol used to deliver messages between parties over its Topic based pub/sub infrastructure. This subtle, but important detail allows users to select the Quality of Service (QoS) that exactly meets their needs, while juggling the many tradeoffs of any engineering decision. For example, the solution may require all messages be accounted for and their delivery guaranteed end to end in a transactional manner, or it may allow messages to simply be fire and forget where there is no guarantee of delivery.
Clearly message throughput and latency (as well as other QoS characteristics) are affected by these and many other choices, and in the case of the first scenario it is reasonable to expect a lower message throughput than in the second scenario. Neuron ESB provides the necessary flexibility for the user to configure the system to support a multitude of different transport QoS’s simultaneously. It is also important to note that the transport protocol (and resulting QoS) can be changed at any time through the Neuron ESB Explorer tool with a simple dropdown box selection; no code or configuration file changes are required, and there is no impact to client code, it is completely transparent.