@roma198001 @Cabecinha1984 That's the idea: components address each other by .mesh.flux name and fluxdnsd resolves them | Hanami
@roma198001 @Cabecinha1984 That's the idea: components address each other by .mesh.flux name and fluxdnsd resolves them inside the app. When the node under a component changes, the name still resolves, so nobody edits DNS by hand at deploy time or after a failover.
Reply to @roma198001: @Cabecinha1984 @RunOnFlux With FluxDNSD, multi-component applications on the decentralized Flux network can communicate with each other securely and rapidly.