-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #433 from equinor/423-add-info---when-not-to-use-r…
…adix added when not to use Radix
- Loading branch information
Showing
2 changed files
with
20 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
--- | ||
title: When to not use Radix | ||
--- | ||
|
||
## When to not use Radix | ||
|
||
There will be certain circumstances that will Radix not suitable for your applications, some of these can be | ||
|
||
- On-prem connectivity is required | ||
- Need to use own terraform configurations | ||
- Need to use own helm charts or flux | ||
- Need to use DAPR | ||
- Need to use sidecars | ||
- Need to have direct access to Kubernetes components (pods, secrets, etc.) | ||
- Need low-latency persistant storage (eg. databases and similar) | ||
- Needs to accept traffic other than HTTP (eg. mqtt or UDP) | ||
- Need to run own operators (e.g. redis operator to run Redis database in cluster) | ||
|
||
However there are workaround for many of these cases, use the Radix community to ask for guidance. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters