My name is Harini Gunabalan and I am the Product Manager of SAP Cloud Platform Document Service. I had a recent discussion with an oil industry customer, who developed a business application on SAP Cloud Platform. This app required a storage service to persist business documents. There were questions around how to consume SAP Cloud Platform Document Service, what are the storage limits provided by this service, and if it all this was the right service to use. Hence, I would like to share a particular use case on how we consume Document Service at SAP and at what scale we use this service.
For those of you who did not know about this service, SAP Cloud Platform offers Document Service as one of its data storage capabilities. Document Service provides the ability to store documents, files, images, videos and more with enterprise grade security. It serves as SAP Cloud Platform’s backbone for enterprise content management. Apps running on SAP cloud Platform can consume it through the OASIS standard protocol called Content Management Interoperability Services (CMIS).The high level architecture of how Document Service is consumed by apps is shown in the picture below:
It is quite exciting for us to announce that SAP ONE Support Launchpad now uses SAP Cloud Platform Document Service to store all attachments of customer incidents. The SAP ONE Support Launchpad provides a central and personalised entry point to service and support as shown in the image below. Customers use the SAP ONE Support Launchpad to operate and maintain their SAP solutions, by creating tickets and interacting with SAP Experts via chat to resolve issues. Most of these incidents have attachments included and these attachments are in turn stored in SAP Cloud Platform Document Service.
Alright so far everything sounds great. So typically for use-cases involving files, business documents, images, videos and so forth we can use this service. But what about storage and scalability limits? So let me provide a few numbers to understand the scale of this particular use-case. SAP ONE Support Launchpad is used by over 90,000 unique users each day and 600,000 unique users every month from more than 180 countries worldwide. Around 10,000 attachment files are created every day by this Launchpad on Document Service and nearly 350,000 queries per day are executed by the Document Service to support the SAP ONE Support Launchpad. The below image shows the list of apps of the Launchpad that use Document Service.
The last app shown in this list is another significant application within the SAP ONE Support Launchpad called the SAP Transformation Navigator. This is a Hasso Plattner Founders’ award-winning tool and this tool helps our customers chart their transition to an SAP S/4 HANA-centric environment. SAP Transformation Navigator also makes use of SAP Cloud Platform Document Service to persist files and documents. There are several other use-cases that consume SAP Cloud Platform Document Service such as SAP Document Center, SAP Help Portal, S/4 HANA attachment service and so forth.
Overall to serve all SAP and customer applications, the SAP Cloud Platform Document Service handles over 70 million global requests per day. This scalability is achieved by the efficient, file storage and retrieval mechanisms offered by the SAP Cloud Platform Document Service compared to the traditional databases. Here is also a video tutorial on how to build a sample application on SAP Cloud Platform that consumes the Document Service. Data isolation and multi-tenancy are also supported by this service. Although Document Service includes certain limits such as 5 million objects per tenant repository, 100 tenant repositories per sub-account and so forth, these limits can be extended depending on the use-case and business scenario as explained in the documentation.
I hope that this gives a useful insight into how and what type of use-cases can be built around SAP Cloud Platform Document Service. If you are already using it or if you would like to use it, I would be delighted to hear about your experiences, insights and challenges as comments.