Content Services Platform

The relatively new term Content Services Platform (CSP) is the name that has been given to the successor of Enterprise Content Management. CSP aims to allow companies to meet the changing needs of businesses and the marketplace. Stepping into the place of monolithic ECM applications is the conceptual idea that “everything is”, or could be “a service”.


What is a Content Services Platform?

A CSP can be understood as a changing number of micro-services that are configured either as a complete product or as an individual application. The number is considered to be “changing” because new services can be established at any time. This is due to the conceptual design of the Content Services Platform, which focuses on flexibility. At the heart of a CSP is the active use of fixed, language-independent interfaces (APIs) that connect frontends and backends with each other. In this way, almost any services and content types can be managed using a Content Services Platform.


Characteristics and Benefits

  • Individualization: Front-ends can also be created without programming knowledge using the low-code tools of your choice. Web and process construction kits as well as SDKs and fixed APIs are available for this purpose. In this way, services can be established easily. A good example of this might be shipment tracking, which is addressed via a REST API. The frontend doesn’t require that much knowledge. It just needs to be able to accept a character string and to send it to the REST-API via Get-Request. In this example, the configuration of the process steps behind the API of the Content Services Platform is irrelevant. It is important, however, that the frontend can both send the request and display the result.


  • Scalability: The experiences of recent decades have shown the following to be true: Volumes of data grow exponentially, and when business is going well, the number of accesses to the system increases. During everyday business, a problem then arises that isn’t so easy to solve. This experience has been taken into account on a conceptual basis in the Content Service Platforms. Increasing demands, e.g. from docker containers, are therefore easy to compensate for.


  • Flexibility: Everything is a service, and according to this philosophy, which recalls the Unix design principle of “everything is a file”, microservices are the core component of a Content Service Platform. They are called microservices as they “only” complete one task – also in the Unix sense – but they complete it very well. Flexibility comes into play here because in this case, more complex services are made up of independent microservices. Their communication takes place via language-independent APIs, referred to as interfaces. The services are largely separate from each other and complete a small task. At the same time, the advantage of this design is that a single, failing microservice won’t bring the entire application to a standstill.


  • Integration:  As the communication of the different services takes place via language-independent interfaces, a typical feature of modern content service platforms is their power of integration. This means that new microservices can be established more quickly. This is also important for the integration of older ECM services, which can then be integrated into the Content Services Platform iteratively and in small steps.


  • Reliability: It is naturally the case that the cloud plays a very special role in the context of a content services platform. In this respect, reliability and location-independent access are the key words. Both must be guaranteed for business-critical services – and that is exactly what the cloud delivers. Despite all skepticism, moving the Content Services to the cloud makes sense. The existing Content Services can then be made available via the Web. It goes without saying that well configured Content Services Platforms are characterized by the fact that they provide a solution for all operating models. Modern Content Services are available as cloud, on-premises or via a hybrid solution.


Learn more about these platforms in the newsroom.

This might also interest you:
Webinar: Material Management via SAP - an Airbus Story
Webinar: Material Management via SAP – an Airbus Story
Webinar: Drivers for Digital Material Master Process in SAP
Webinar: Drivers for Digital Material Master Process in SAP
Digital Platform & Application - Introduction and Use Cases
Webinar: Digital Platforms & Industry 4.0
Back to topic Next Post