Skip to Content
Technical Articles

A Full Stack Developer life -> Before CAP vs After CAP

I’m sure you’ve heard or read about the new application programming model for SAP Cloud Platform & Core Data & Services (CDS).There’s been a lot of interest around the new Application Programming Model for SAP Cloud Platform

What actually is the SAP Cloud Application Programming Model?

Briefly, the Application Programming Model for SAP Cloud Platform is a framework of tools, languages and libraries, some from SAP, some open source. With these tools, languages and libraries you can efficiently and rapidly build enterprise services and applications in a full-stack development approach.

CDS are part of SAP’s new programming mode & the backbone of the SAP Cloud Application Programming Model. It provides the means to declarative capture service definitions and data models, queries, and expressions in plain (JavaScript) object notations. CDS views push the logic to the database, plus to the client-side as well.

By using declarative approaches like CDS, plus a combination of enterprise-grade tools and services, and a golden path of best practices, allowing you to focus on your domain problems to solve instead of wasting time and efforts in technical disciplines and hard-to-maintain boilerplate code, relieving you from tedious technical tasks. Therefore CAP greatly increase developer productivity and speed up the development process. This means we significantly reduce time to market. Moreover, this ensures many essential non-functional features, like multi-tenancy, extensibility, supportability and maintainability.


In my experience



In this blog post I would like emphasis on development effort to create a business service i.e functioning CRUD+Q OData service using Apache Olingo frame work vs CAP

Example: An application developer was given the task of creating car services on SAP Cloud Platform that integrates with SCP Hana database.

Using Olingo we needed to write a lot of boilerplate code

Source Code using Apache Olingo + Java  :





Source code using SAP CAP :

With less lines of declarative code you can spin up a fully formed CRUD+Q OData service, and adding custom handlers is also only a few lines of code.

CAP basically an extension of the Olingo framework which eliminated the boilerplate code required for setting up a OData application & implement OData services.The CAP Java stack has a Persistence Service that provides out-of-the-box capabilities to store and retrieve entities from a database. Therefore no custom coding is required for this. The entities defined in your CarService will be automatically served via OData.

CAP applications use Core Data Services (CDS) to describe: declarative capture service definitions and data models

Only two steps are required to implement services

  • Define data structures by using entity definitions
  • Define how this data structures are consumed by using service definitions

You can create the UI for your business application using SAP Cloud Application Programming Model, SAP Web IDE Full-Stack and the Annotation Modeler to add UI annotations.

The Next generation Java stack is able to tightly integrate with Spring Boot, which provides a lot of features out of the box. This means, Spring Boot will be your runtime container.

Thanks for reading .

Be the first to leave a comment
You must be Logged on to comment or reply to a post.