Project updatePublished: 1 min readSample
Ecosystem Config: notes on how consumers read the registry
Each consumer keeps only the fields it needs. Questions worth answering before adding more consumers.
Consumers fetch the published registry at build time and write a small projection. This journal is one of them: it reads project names, destinations and deployment URLs so that project updates never hardcode them.
- Should consumers share one sync script, or keep owning their own?
- How should a consumer react to a destination it doesn't recognise?
- When is a project's tagline worth showing outside Gateway?
