This document discusses hybris' Commerce as a Service (CaaS) platform built on Cloud Foundry. Some key points:
- Hybris is an SAP company that provides an on-premise multi-channel commerce platform. It wants to offer CaaS to help customers develop and sell commerce services/apps in the cloud.
- CaaS will be API-enabled and allow customers to evolve existing websites, develop integrated services, or build new consumer apps.
- The architecture involves SAP's Hanna Cloud Foundry hosting core CaaS services, third-party services, and customer-developed apps/services.
- Hybris has been developing CaaS since early
3. ABOUT HYBRIS
Founded in 1997, since 2013 an SAP company
On Premise Multi Channel Enterprise Commerce
Platform
We operate in 15 countries and serve over 500
customers
Gartner and Forrester ranked us “leader” and placed us
among the top two or three commerce platforms in the
world
4. A cloud platform that allows
everyone to easily develop, extend
and sell commerce services and
apps.
5.
6. CAAS - API ENABLED STRATEGIES IN THE CLOUD
1. Evolve an existing Website into a full-blown commerce platform in
the cloud
2. Focus on developing a set of seamlessly integrated services that
enrich existing [commerce] systems
3. Build game changing, consumer focused functionality and apps
7. HYBRIS AS A SERVICE – KEY ASPECTS
API First & Mobile First
OPEN TO EVERYONE - to increase reach and help innovation
INTEGRATED MARKETPLACE – to integrate monetization as a
motivator
OPEN TECHNOLOGY STACK – to increase reach and help
innovation
8. SAP IaaS
[y] Cloud Foundry run by SAP Hanna Cloud Platform
CaaS
Service
CaaS
Service
CaaS
Service
CaaS
Service
CaaS
App
CaaS
App
CaaS
App
CaaS
App
Core
Service
Core
Service
Core
Service
Core
Service
API Mashups
Market-
place
Open
to
Everyone
Dev
Portal
ARCHITECTURE OVERVIEW
Backing
Service
Backing
Service
LoggingMonitoring
11. PROJECT HISTORY
Kicked off [y]aaS in February
Developer Boot Camp in mid February
12 FACTORS
Stateless Services
Backing Services
Explicitly declare and isolate dependencies
MICROSERVICES
Small services with clear responsibility and minimal
dependencies
Independent release cycles between services
Choose the best solution for the “problem”
12. PROJECT HISTORY
March 1st Running CF on AWS
May 2nd Instance of CF on AWS EU
~ 35 different Apps running on CF
8 Different buildpacks
End of June 1st internal Release of our Services
13. Key Technology ”ZOO” used by [y] Services
Cloud Foundry Apache ZooKeeper Java
BOSH Apache Kafka Groovy
Logstash Apache Cassandra Jersey
Riemann Elastic Search REST
Twitter Bootstrap Mongo DB JSON
APIgee Orient DB jetty
Spark Netflix Hystrix RxJava
RAML Drools OAuth2
DocPad Redis Angular.js/Node.js
Operated by 2
This talk is about how we leverage CF for our Commerce as a Service Product
1997 Founded in Munich – 2011 Merger with iCongo Montréal – since last year an SAP company
Core business is an highly customizable On Premise enterprise eCommerce multi channel solution as well Product information Management solution
Well known brands like Nikon, 3M, GE or Levis
the term hybris means "extreme pride or arrogance”
When hybris was founded, we were not the first to explore e-commerce, but we had the advantage of being young and ambitious. We decided to challenge the "gods" and succeed. But we also knew that it was going to be quite a journey.
Think and work with hybris - judge and review your work with a reflective mind afterwards.
1997 Founded in Munich – 2011 Merger with iCongo Montréal – since last year an SAP company
Core business is an highly customizable On Premise enterprise eCommerce multi channel solution as well Product information Management solution
Well known brands like Nikon, 3M, GE or Levis
the term hybris means "extreme pride or arrogance”
When hybris was founded, we were not the first to explore e-commerce, but we had the advantage of being young and ambitious. We decided to challenge the "gods" and succeed. But we also knew that it was going to be quite a journey.
Think and work with hybris - judge and review your work with a reflective mind afterwards.
But today I am not here to talk about our Enterprise Platform, I am here to talk about our Commerce as a Service product we are currently developing and which we run on Cloud Foundry.
As you can read in our mission statement, we are focusing on services and apps rather than one integrated platform.
I like the logo because it shows exactly our micro service concept we are focusing on and which together creates one big picture and depending on how you combine those micro services you will get a different picture
What are our services and apps we are developing?
The core or the center are our API based REST service (yellow) They are the heart of our platform. They are getting consumed by all the surrounding Apps e.g.
On Demand Website
Admin UI (back office UI)
Market Place
Our developer Portal
Or by external source like your Company Website, Mobile Apps or instore Apps.
We provide different packaging models depending on your needs e.g. just API usage to enrich your existing Shop Experience or Complete shop with our On Deman Website
This is how envision to use our Commerce APIs
Since hybris is mainly perceived as an ECP we often find our selfs explaining what the key aspects of our SaaS solution and what our drivers are.
Here you can see our technology stack
At the bottom we have our infra structure service and our backing services
Within cloud foundry you can see our services and apps running
Our Core service provide fundamental services to higher services like Commerce services (orange)
Service Mashups will be the primary method to compose and aggregate services
used for aggregating service calls for context and device specific views as well as for composing service flows e.g. checkout
they are reactive, asynchronous, dynamic, and resilient
and available on the marketplace
Private PaaS
Backing Services Managed through BOSH
Specific core services hide Backing Services from consumer services
Multi Tenancy handled by [y] services
Before start to talking about our Commerce as a Service Solution I want to give you a bit of a background what we have achieved so far and what our next steps
Because we as an organization had On Premise in our DNA, it was necessary to restructure our Development departments and split the On Premise Teams from the On Demand teams.
12 Teams with an average of 5 members
Developer Boot Camp mid February –
2 Weeks of Prep
Deployment experience
12 Factor Architecture – Port binding – backing services – dependency bundling
Micro Services
Deis.io
Since March working on Cloud Foundry ~ 35 different kind of Apps – Services
Before start to talking about our Commerce as a Service Solution I want to give you a bit of a background what we have achieved so far and what our next steps
Because we as an organization had On Premise in our DNA, it was necessary to restructure our Development departments and split the On Premise Teams from the On Demand teams.
12 Teams with an average of 5 members
Developer Boot Camp mid February –
2 Weeks of Prep
Deployment experience
12 Factor Architecture – Port binding – backing services – dependency bundling
Micro Services
Deis.io
Since March working on Cloud Foundry ~ 35 different kind of Apps – Services
Before start to talking about our Commerce as a Service Solution I want to give you a bit of a background what we have achieved so far and what our next steps
Because we as an organization had On Premise in our DNA, it was necessary to restructure our Development departments and split the On Premise Teams from the On Demand teams.
12 Teams with an average of 5 members
Developer Boot Camp mid February –
2 Weeks of Prep
Deployment experience
12 Factor Architecture – Port binding – backing services – dependency bundling
Micro Services
Deis.io
Since March working on Cloud Foundry ~ 35 different kind of Apps – Services