Why enterprise need twin, and how Mithril dey provide am
Production no be di correct place to learn who fit reach sensitive system, how refusal dey look, or weda di cluster wey dey run na di one wey dem declare. Twin dey keep dose names and e no dey apply di result. Mithril dey turn dat twin to document: reverse-domain components dey compose, one run dey return di response and di decision, and dem dey check cluster against wetin dem observe without to start am.
Dis article na machine translation.
Company need twin because di questions wey matter no fit ask for production. Who fit reach system wey hold customer data. How denied call dey look when quota don finish. Weda di cluster wey dey run today na di cluster wey dem declare. Production na where customers, payments, and identity don already dey live. To use am as di place to learn dose answers dey join curiosity to outage. To freeze every change until committee sure na di other failure: di estate dey still move, and di model of am no dey move.
Twin na second copy of dat estate with di same names and hard rule say nothing dey apply. Di principal, di bucket, di queue, and di cluster real enough to answer di question. Di effect stop for di copy. Security, platform, and architecture fit rehearse allow, refusal, fault, and drift before any of dose reach di account wey dey bill customers.
Mithril dey make di twin one document, no be second cloud. Each part of di estate na component wey im reverse domain name, and components dey compose. Identity, authorization, quota, consistency, fault, and TLS dey under di service wey need dem. One run dey waka dat chain and return two things wey di caller fit keep: di response wey client go see, and di decision wey produce am. Di applied flag dey stay false. Di runtime no dey open socket, and document wey name live host or secret dey refuse before e run.
Di same boundary cover di cluster. Docker and Podman dey wrap as Mithril document wey talk which services suppose exist and how dem depend on each other. To render dat document dey produce di Compose file. To check am dey compare di declaration to wetin dem actually observe. Di check no dey start containers. Di company dey get rehearsal of im own estate, beside di engines wey already dey speak di cloud protocols, with record of wetin dem decide and wetin dem deliberately no apply.