From 59f7050fc5ec1775689314f6e2da168e92db1c2b Mon Sep 17 00:00:00 2001 From: Johannes Vogt Date: Mon, 2 Jun 2025 18:04:14 +0200 Subject: [PATCH 1/3] release microservices guide --- guides/deployment/microservices.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/guides/deployment/microservices.md b/guides/deployment/microservices.md index eeccfdb83f..a17e1cf5b5 100644 --- a/guides/deployment/microservices.md +++ b/guides/deployment/microservices.md @@ -1,6 +1,7 @@ --- synopsis: > A guide on deploying SAP Cloud Application Programming Model (CAP) applications as microservices to the SAP BTP Cloud Foundry environment. +status: released --- # Microservices with CAP @@ -10,10 +11,10 @@ A comprehensive guide on deploying your CAP application as microservices. [[toc]] -## Create a Solution Monorepo +## Create a Solution Monorepo Assumed we want to create a composite application consisting of two or more micro services, each living in a separate GitHub repository, for example: - + - https://github.com/capire/bookstore - https://github.com/capire/reviews - https://github.com/capire/orders From 6a57c62d2378a89b607a4750642fbd300f116fe3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Jeglinsky?= Date: Tue, 3 Jun 2025 15:04:32 +0200 Subject: [PATCH 2/3] Update microservices.md --- guides/deployment/microservices.md | 1 - 1 file changed, 1 deletion(-) diff --git a/guides/deployment/microservices.md b/guides/deployment/microservices.md index a17e1cf5b5..fd91005936 100644 --- a/guides/deployment/microservices.md +++ b/guides/deployment/microservices.md @@ -907,7 +907,6 @@ resources: #### Subsequent updates -- TODO... - Whenever one of the projects has changes affecting the database, that triggers a new deployment of the `shared-db` project - `git submodules` gives you control of which versions to pull, for example by `git branches` or `git tags` - Ensure to first deploy `shared-db` before deploying the others From 58df498a13fd89399cb6072d8b35db0ab3e45414 Mon Sep 17 00:00:00 2001 From: Johannes Vogt Date: Tue, 3 Jun 2025 17:23:37 +0200 Subject: [PATCH 3/3] tidy up subsequent updates section --- guides/deployment/microservices.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/guides/deployment/microservices.md b/guides/deployment/microservices.md index fd91005936..df9cfd6e7f 100644 --- a/guides/deployment/microservices.md +++ b/guides/deployment/microservices.md @@ -907,11 +907,7 @@ resources: #### Subsequent updates -- Whenever one of the projects has changes affecting the database, that triggers a new deployment of the `shared-db` project -- `git submodules` gives you control of which versions to pull, for example by `git branches` or `git tags` -- Ensure to first deploy `shared-db` before deploying the others - - +Whenever one of the projects has changes affecting the database, the database artifacts need to be deployed prior to the application deployment. With a single `mta.yaml`, this is handled in the scope of the mta deployment. When using multiple deployment units, ensure to first deploy the `shared-db` project before deploying the others. ## Late-Cut Microservices