Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added when not to use Radix #433

Merged
merged 1 commit into from
Dec 23, 2024
Merged
Show file tree
Hide file tree
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
19 changes: 19 additions & 0 deletions public-site/docs/start/not-radix/index.md
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.
1 change: 1 addition & 0 deletions public-site/sidebars.ts
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ const sidebars: SidebarsConfig = {
'start/workflows/index',
'start/radix-clusters/index',
'start/onboarding/index',
'start/not-radix/index',
],
},
],
Expand Down
Loading