I tend to get a lot of questions on how the basics of SAP Development in the Cloud work.
If you are starting or would like to understand better how everything fits together, then this blog is for you.
Let’s start with this architecture diagram. It basically describes how the application architecture works in SAP BTP. Although there are different environments (Kyma, ABAP, Cloud Foundry and the deprecated Neo), the most common patter is to deploy to the **SAP BTP, Cloud Foundry Runtime environment (see setup here).**
If we go to our trial account, we can see the environment listed there, we will be able to see our applications deployed there as well.
Ok, next, if in the diagram we see the letter A, that points to SAP Business Application Studio (BAS). SAP BAS is the IDE (Integrated Development Environment) where we will build the applications. (See setup here) This is a subscription that we can activate, and then access, here we can create our applications.
In this case, we will talk about Multi Target Applications (MTA), that are basically applications that group micro-services and serve as a single point of control to follow the application lifecycle. When we ‘build’ our application, all the elements that represent the Microservices (including the UI, the backend logic, the database artifacts and the routing) will be compiled and saved under one file that we can later deploy.
