The MethodFactory Envoy Enterprise Service Bus

MethodFactory Envoy
MethodFactory developed Envoy to fill a space in Enterprise Application Integration, which is needed by many of our clients for eCommerce and other systems.  MethodFactory Envoy is a solution designed to route messages from one system to another through a common conduit (a.k.a. an Enterprise Service Bus).  Other products exist in this space but have grown more complicated to use and more expensive to own over time.

Envoy not only routes data (in messages) from one system to another; much like email, it can deliver the same message to many different systems.

Uses of the MethodFactory Enterprise Service Bus include:

Scheduling of Tasks

  •     Importing of inventory
  •     Importing of product catalog changes
  •     Exporting product feeds to marketplaces
  •     Integrating with 3rd party search systems
  •     Integrating with 3rd party product ratings & reviews services

Asynchronous handling of  user or system-initiated events

  •     On order creation, sending a copy of the order from the eCommerce website to the ERP system
  •     On customer information change, send a complete copy of the customer’s information to a CRM system
  •     On order status change, import the change from the ERP system into the Web Commerce system

Sending out event-driven email notifications like: order received, order is processing, order shipped, etc.

Receive and route orders and other messages from systems such as EBay, Amazon, Google, etc.

MethodFactory Envoy feature points include:

  •     Built-in scheduler to run scheduled tasks
  •     Runs on a separate server to reduce the load on the website
  •     Is configurable to pick up and route messages from one system to another
  •     Standardized exception handling
  •     Can route the same message to multiple systems
  •     Retention of the original message format.  In case a custom component fails on processing the message, Envoy stores the original message for a configured period of time
  •     Workflow
  •     Messages that failed to be consumed by a system due to an error can be re-sent to the receiving system. This is useful if the problem was not the content of the message but rather a custom processor that had incomplete or invalid logic
  •     Configurable batched error summary notifications

Related Posts