Got the hang of SAP hybris YaaS – a SOA-based cloud solution for e-commerce. Managed to do some coding and customization. Last week, we launched an Open Beta for the SAP partner community.
An extremely interesting, somewhat trendy, and visually appealing concept.
lightweight storefront @AngularJS + API first + Scalability + EJB/COM + RAML + MQ + Pivotal Web Services / Cloud Foundry
The storefront is an extremely lightweight solution, in the out-of-the-box example it has no server-side scripts at all, it’s built on AngularJS, which is a JavaScript framework. The server side is the yaas.io service, which acts as a container for RESTful API – it proxies requests to real services, hosted on platforms such as pivotal.io, incorporating its own checks. Some of these APIs are offered as hybris-as-a-service, covering both core and e-commerce functions.
Development involves creating custom APIs, publishing them as services in the cloud, and connecting them to each other and to the storefront.
You can subscribe to other people’s APIs, for which there is a marketplace. The market allows you to publish your publicly beneficial APIs and make money from them (not yet possible).
For example, you subscribe your store to an API from the Email library, and voila, you have the cloud capability to send emails, with a corresponding REST interface.
Subscribe your store to a search API – and you have the cloud ability to search your data. There’s a choice between different search engines. Facets are available too.
Created your own service for KLADR address verification – and you earn by others using it.
Of course, connecting any new service requires you to hack the storefront on AngularJS quite substantially, but it’s all documented. Or, add interactions to your own APIs.
Ultimately, the store consists of a lightweight storefront + a set of APIs on different servers, loosely coupled to each other + a lightweight, extensible admin panel on yaas, which interacts with the same APIs for data retrieval/modification. Essentially, there’s no core system – the system consists of many small e-commerce blocks scattered across different domains, servers, clusters (though currently all hosted on the same platform). Each can be individually enhanced.
APIs are hosted on Pivotal.io/Cloud Foundry. There is a convenient mechanism for publishing APIs to the cloud, as well as an easy way to provision resources for it.
API development uses the RAML language, allowing easy expansion of your services with library capabilities, known as RAML traits – “features” that can be applied to new APIs, like adding filtering or paging to APIs that return records sets.
There’s also its own cloud middleware software for MQ, for communication between APIs and external systems like ERP. There’s a mechanism for extending data in the API framework. Data behind the API is handled by MongoDB, but it’s invisible as access to objects is through REST interfaces.
@[658732965:2048:Andrey Tatarinov] there’s something very corporate about it @[1431739380:2048:Grigory Bakunov] @[100001168004708:2048:Erik Babadzhanov]
Apart from the advantages (and I haven’t listed them all), I know the drawbacks. The vendor’s model is not yet fully developed, neither technically nor business-wise. Still figuring out the details. How soon will we implement a system based on this technology? Are there similar themes in the market?
Hi, I'm Rauf Aliev. 