As seen in the unit for SAP Cloud Application Programming Model, the idea is to allow open tooling for the Application Development.
Following this concept and to allow greater flexibility in Application Development .
From a Development standpoint, SAP Business Application Studio is used as the preferred tooling for Application Development when using SAP CAP, at the same time other tools are also allowed. example Visual Studio with CDS Extension, Eclipse,Docker,Jupyter notebooks.
From a Deployment standpoint, SAP CAP allows two deployment options.
- Local :
The idea with the local development is to provide quick development and test cycles
For Local developments, SAP CAP automatically bootstraps an SQLite in-process and in-memory database by default — that is, unless told otherwise.
While this isn’t meant for productive use, it drastically speeds up development turn-around times, essentially by mocking your target database, for example, SAP HANA.
- Persistence :
- SQLite :
Instead of using in-memory, we can also use persistent databases. For example, still with SQLite:
The difference from the automatically provided in-memory database is that we now get a persistent database stored in the local file
- SAP HANA Cloud :
Once the development and tests are complete the developments can be deployed to the HANA Cloud Database alternatively you can directly start with this option. A set of prerequisites has to be followed when deploying the developments to SAP HANA Cloud and this will be mentioned later.
- SQLite :