This project is read-only.

Product highlights

  • XML Message based services. Does static content based routing by default, however being message based, you can plug in your own service to do whatever type of routing you like - most likely using XPath expressions would be an easy thing to do.
  • Plug-In framework for building business services and integration components
  • Resulting services exposed via SOA principles and best practices, and multiple transports (SOAP WSE3, WCF, raw HTTP), so you won't have a problem with SOAP versions etc.
  • Client side assemblies abstract the Envelope and commnication details, so all you have to worry about is populating your business data and adding it to the ESBEnvelope.
  • Attachment handling details abstracted. Just add the file path to the ESBEnvelope and let the transport adaptors worry about getting it to your service efficiently.
  • Work at the message level (ESB.NET BSDL) for your business services. All SOAP Web services automatically exposed through single WSDL, so you never need to touch WSDL again. Wrapped Document/Literal message format. WS-* and WS Basic Profile 1.1 compliant messages.
  • Abstracted ESBEnvelope (or create your own envelope) and helper classes to make message manipulation (documents and attachments) a snap. Concentrate on the business issues whilst the ESB libraries take care of all the lower level details.
  • Configurable execution of plug-in services modules.
  • Visual Studio template project & class for building services
  • Centralised management of all services
  • Logging
  • Configuration (via application blocks)
  • Hot configuration means you can change log levels, add/remove new components without taking down the running system - eg. change log level to troubleshoot errors, or replace faulty component at runtime without taking system down.
  • Option(default) to deploy add-ins in separate folder to .NET Bin directory, to make your development & deployment easier.
  • Request level logging across instances
  • Lightweight, multi instance support on single server, distributed to allow for a true ESB, however each instance is much smarter than a plain old web service
  • Distributed, Network Load Balanced and Basic Routing allows for a reltively easy provisioning of a Business Oriented 'Services Grid' like deployment architecture
  • Performance optimised (~150 (test) rq/s on a 1.7GHz Pentium-M notebook, ~300 (test) rq/s on a Dual 3.0GHz P4 with HTTP & WCF Transports and 1k sample message and test adaptor), near linear scalability with CPU & NLB.
  • Developed over past 7 years on small, medium & large projects which guarantees it will be suitable for your size project. Can be used from simple websites to complex systems integration projects, all with the same integration architecture.
  • Comprehensive Management Console for remote management (separate URL from running services).
  • Best practices MS Application Blocks used to keep core & plug-in functionality extensible & adequately decoupled.
  • Client-side components also included (highly recommended) to abstract away message creation and calling services. Single URL to configure Web Service Endpoints.
  • Simple/Remote Message testing features as part of the web based management console for functionality/regression/build verification testing, as well as specific message testing console for testing services. No need for test harness etc.
  • IIS6/ASP.NET hosted so you can use all those nice IIS & ASP.NET features for managing your Services. eg. Web Garden, Process Recycling etc.
  • Rudimentary BAM with SQL Server 2005
  • Easy routing of requests amongst servers. Use a centralised SQL Server logging server for a complete request trace amongst distributed servers, allowing you to easily partition ESB.NET instances according to function & performance requirements amongst your physical servers, and not having to worry about the Service Bus' traces becoming fragmented.

Last edited Sep 5, 2007 at 3:37 PM by MINAS, version 1


No comments yet.