Document BYOC #119
Document BYOC #119
Conversation
jordanstephens
force-pushed
the
jordan/launch-prep
branch
from
f8f81da to
96083f4
Compare
jordanstephens
requested review from
raphaeltm,
lionello,
Prakash-Sundaresan and
commit111
There was a problem hiding this comment.
See detailed comments.
Also, we should replace all references to "AI assistant" with "AI agent" - e.g. in https://docs.defang.io/docs/intro
| | Feature | Development | Staging | Production | | ||
| |-|-|-|-| | ||
| | Build Resources | Builds will be run with 2x vCPUs | Builds will be run with 2x vCPUs | Builds will be run with 4x vCPUs | | ||
| | Databases | Defang will provision resources optimized for burstable memory | | Defang will provision resources optimized for production | |
There was a problem hiding this comment.
Should we say something about behavior on 'compose down'?
There was a problem hiding this comment.
Yes. I think we should create a Databases concept topic where we can discuss the subtlety more carefully 👍
docs/use-cases/use-cases.md
Outdated
| ## Data Stores | ||
|
|
||
| Defang is not a good fit for data stores like databases, caches, and message queues. These types of services are designed to be long-lived and to store data. Defang is primarily designed for stateless workloads, and it's not a good fit for stateful workloads: if a container is replaced, all the data in it is lost. You could probably coerce a data store to work in a stateless environment with certain replication strategies, but it's not a good fit. | ||
| Defang is not a good fit for data stores like databases, caches, and message queues. These types of services are designed to be long-lived and to store data. Defang is primarily designed for stateless workloads, and it's not a good fit for stateful workloads: if a container is replaced, all the data in it is lost. You could probably coerce a data store to work in a stateless environment with certain replication strategies, but it's not a good fit. |
There was a problem hiding this comment.
This is not accurate. We should mention the issue with stateful services and then point to Defang's support for managed storage options - https://docs.defang.io/docs/concepts/managed-storage
There was a problem hiding this comment.
@Prakash-Sundaresan I think you're right. This is no longer accurate because we support managed storage. I do think we should have a place where we caution people against trying to run unsupported data stores until we support volume mounts, though. Like, at the moment people shouldn't be using Defang to run Mongo, or ElasticSearch or anything like that.
…fang-docs into jordan/launch-prep
jordanstephens
force-pushed
the
jordan/launch-prep
branch
from
b202a79 to
3f16324
Compare
Changes in this PR