Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion get-started/grow-as-you-go.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,16 +30,20 @@ After we are prepared for production we can deploy to the cloud. In case of the
cds add mta
```

[Learn more deploying your CAP application.](../guides/deployment/){.learn-more}



## Add Multitenancy

If you are creating a SaaS application you also need to add support for tenant subscriptions and tenant upgrades. When a tenant subscribes, new database containers have to be bootstrapped along with other resources, like message channels. CAP provides the so-called MTX services which do that automatically in a sidecar micro service. You can add all required packages and configurations by:

```sh
cds add multitenancy
cds add multitenancy --for production
```

[Learn more about multitenancy.](../guides/multitenancy/){.learn-more}

::: tip Intrinsic Cloud Qualities
As we see below, we can add qualities like multitenancy or extensibility late in time. This is made possible by the fact that there is no difference between a single-tenant and a multitenant application from content perspective: CAP does all the necessary things, for example for tenant isolation, behind the scenes. Similarly, CAP provides intrinsic extensibility, which means there's nothing you, as an app developer, need to do to enable this.
:::
Expand All @@ -54,6 +58,8 @@ Extensibility is required to allow customers to adapt SaaS applications to their
cds add extensibility
```

[Learn more about extensibility.](../guides/extensibility/){.learn-more}



## Add CI/CD Pipelines
Expand Down