Architecture: SAP Hybris Deployment

This article describes an architecture for deploying
SAP Hybris
on Google Cloud. SAP Hybris is a commerce platform designed for
scalability, high traffic, and high order volumes. The SAP Hybris platform
supports business-to-business
(B2B)
and business-to-consumer
(B2C)
workloads. This article describes the SAP Hybris architectural components for
B2B and B2C deployments and explains how to deploy them using
Google Cloud.

SAP Hybris component architecture

The SAP Hybris platform contains the following components:

A web server for serving static content and directing dynamic
requests, such as
Apache
or
nginx.

To deploy SAP Hybris using GKE, you package the web server, the
core SAP Hybris Java application, and the caching mechanism into individual
Docker containers. Next, you create Kubernetes manifests to map the Docker
containers to the pods and services that you will deploy.

When you use GKE, you create two
Virtual Private Cloud
subnetworks that span multiple zones within a single region:

The first subnetwork contains a GKE cluster for the web servers.

The second subnetwork contains a GKE cluster for the Java
application servers and for the caching mechanism. The second subnetwork also
contains the Compute Engine instances for the search and database
components to minimize latency between the application servers and the
search and database systems. The Compute Engine instances in this
subnetwork use internal-only IP addresses to prevent public access. You use
firewall rules to configure the subnetwork to allow access only from the web
server subnetwork. This configuration adds an additional layer of security to
the components in this subnetwork.

You can configure your SAP Hybris deployment for high availability by following
these steps:

When you use Compute Engine instead of GKE, you create
two VPC subnetworks that span multiple zones within a single
region:

The first subnetwork contains the Compute Engine instances for the web
servers.

The second subnetwork contains the Compute Engine instances for the
application servers, database servers, cache, and search components. The
instances in this subnetwork use internal-only IP addresses to prevent
public access. You use firewall rules to configure the subnetwork to allow
access only from the first subnetwork. This configuration adds an additional
layer of security for those components.

You can configure your SAP Hybris deployment for high availability by following
these steps:

Deploy Compute Engine instances across multiple zones within a single
region.

Deploy the web server and application server instances inside a
managed instance group
to simplify management.

Deploy the caching and search components across multiple zones within the
same region as the application server Compute Engine instances.