Beyond the inherent improvments of an ESB over traditional EAI solutions, Petals ESB uses a best-of-breed approach and open source development model to ensure you have all the essential features; as well as access to the latest generation of ESB technologies sooner, not later. Together with other Petals software, it provides a company everything necessary to build your project, from a traditional integration platform to a service oriented architecture.
Natively Distributed Architecture
Most EAI and ESB solutions are based on a centralized architecture. While this implies simplicity of configuration and maintenance, it also means increased risk of downing the whole infrastructure, in case the middleware crashes. Such an incident would have a serious, if not catastrophic, impact on the business.
Choosing a middleware clusters reduce this risk but adds great complexity to the infrastructure.
Petals ESB chose the third way, using a P2P-like approach: the container can be installed on several machines, each one hosting its set of services, router and shared registry of services.
- high availability, thus SLA respect, thanks to replication of services on several nodes and intelligent routing;
- inherent load balancing.
Learn more on architecture models
Light & Powerful
Petals ESB is entirely modular, making it a light, loosely-coupled platform, without the requirement to deploy to an existing application server. Numerous components are already available for message exchange (FTP, SOAP, REST, POP...) and services creation (POJO, Quartz, XSLT, Talend...)
Standard and Open Source
Petals ESB is one of the few to be fully compliant with the Java Business Integration specification. It makes full use of standards protocols.
As an open source product, you can freely adapt it to fit your need, be it through a new component or container adaptation, or ask any expert to do it for you, without being bound to Petals Link (although we are probably the finest experts on these matters).
Ease of Configuration
Setting up services, orchestrating them, transforming messages, can prove a hassle from middle-sized projects on. Petals Studio greatly facilitates these steps, by providing numerous service creation wizards, import/export tools, a graphical interface to create services orchestrations.
Unable to render embedded object: File (petals-studio-tuto-provides-xslt-1.jpg) not found. |
Unable to render embedded object: File (petals-studio-create-bpel-sketch-10.jpg) not found. |
Ease of Administration
One of Petals ESB's most useful add-on is the [Web Console], web-GUI to easily watch and administer the ESB: deployement of new services units and assemblies, components management, fine-grained technical monitoring, testing facilities.
Unable to render embedded object: File (petals-webconsole_administration-components.png) not found. |
Unable to render embedded object: File (petals-webconsole_monitoring-exchanges.png) not found. |
Unable to render embedded object: File (Test-form-page.png) not found. |
Business-oriented monitoring
While previous items appealed more to developers and system administrators, Petals View is aimed more at non-technical users. Once Petals View has been set up and connected by the former, end-users can further configure fine-grained, detailed business reports on any message exchange going through Petals ESB. With this, they can easily follow their business procedures, identify any problem and use this data to build process efficiency analyses.
Business-oriented services management
In contrast with the Web Console, which allows technical deployment and management of services, Petals Master provides a graphical way to manage services from a business point of view. Associate services to roles, users and company to build a structured business-oriented view of all your services, document them with attached documents. All of this allows better business management, processes improvement and optimal reuse of services. Thus ensuring a proper evolution of your infrastructure.
|
|
|