Enterprise Service Bus (ESB)
The Enterprise Service Bus (ESB) is the engine that pulls data from backend systems (SAP PI/PO) and other systems, and pushes data and orders from commerce channels to back-end channels, and shares stock information across channels. You can think of the ESB as a giant high performing connector.
The applications within your commerce IT infrastructure should focus on their core tasks, for example:
- Webshop platform: great consumer shopping experience resulting in high performance
- App: tailored mobile user experience for a consumer
- ERP: Manage company operational and financial processes in a structured way
- Loyalty: reward customers across channels
- CRM: manage and segment customer data to provide optimal offers
All applications share data and require connections – about products, prices, promotions, orders, loyalty credits, etc. A middleware solution like ORP (also called ESB) specializes in managing real-time data flow and connecting all applications. It avoids a spaghetti infrastructure in which applications are used to perform tasks outside their core scope. The wolfpack ESB is a technology enabler. Once installed, it allows for fast and easy integrations of new (or changed) applications in the overall IT commerce structure
The Enterprise Service Bus consists of several microservices (APIs) including:
Order API, Stock API, Product API, Loyalty API, Promotions API, Customer API and Billing API.
Security using Microsoft Key Vault
The ESB is hosted on the Microsoft Azure Service fabric. The microservices based set-up ensures optimal scalability, which ensures the platform can handle the highest order peaks. The wolfpack ESB uses Microsoft Key Vault technology, in which for each transaction a unique token is created.
- Security uses Microsoft Key Vault technology
- Every transaction uses unique temporary token that is generated for registered devices and used to get access to information via APIs
- Applications have no direct access to these cryptographic keys
- Future proof: in line with General Data Protection Regulation (GDPR) from May 2018
- No user names and passwords inserted in the code