Best practices
This section gathers the trade-offs to know to get the most out of Ecosystem in production. It complements the functional documentation: it does not explain how to use a feature — the Guides do — but when and why to use it a certain way.
What you'll find in this section
| Page | Trade-off covered |
|---|---|
| Environment management | Ordering and marking environments for a safe deployment cycle (DEV → STAGING → PROD). |
| Organization with Apps and Tags | Structuring Apps, tags and naming for readable mapping and search. |
| Dictionary management | Centralizing per-environment variables and choosing between dictionary and secret. |
| Authentication method management | Centralizing an authentication scheme and securing secrets. |
| Data mapping | Transforming data between systems: JSONPath extractors vs Code node, variable naming. |
| Error management | Anticipate, capture, analyze and resolve incidents. |
| Usage patterns | Choosing the right integration pattern (scheduler, import, events, API exposure). |
Go further
See also: User guide