Rename `storages` Section to `dependencies` in Configuration
Closed this issue · 2 comments
The storages section in ftl.yaml includes services beyond storage systems, such as databases, message queues (RabbitMQ), search engines (Elasticsearch), and caches (Redis). To better reflect the variety of services and align with industry standards, I propose renaming the storages section to dependencies.
Justification:
- Clarity: The term "dependencies" accurately represents all external services required by the application.
- Inclusivity: Encompasses all types of services without limiting to storage.
- Industry Standard: Aligns with common terminology used in configuration files and package managers.
Hi, I'm Derrick, I've worked on a few deployment systems before, and this project appeals to me due to its simplicity!
I have a comment on your proposal.
While I understand the logical concept of "dependencies", I'm struggling to see the concrete difference between a "service" and a "dependency", as they could be synonymous.
A "service" could be a complete service definition, or a partial definition which could be listed as a dependency for other defined "services" in the configuration.
Logically one service is a dependency of another, but at a concrete definition level, the dependency could just be another "service" definition.
Thoughts?
The logical difference is that services are built from the source code in your repository, while dependencies are not.