The Twelve-Factor App: the guide every system should follow (but few do)
Se você já trabalhou num sistema que funcionava perfeitamente no seu computador mas quebrava assim que ia pra produção, ou já se irritou com uma atualização que exigiu reconstruir tudo só porque mudou a senha do banco de dados, você já sentiu na pele o problema que o Twelve-Factor App tenta resolver. Essa ideia surgiu por volta de 2010, dentro da empresa Heroku, com Adam Wiggins à frente. Na…
The Twelve-Factor App, an idea born at Heroku in 2010 led by Adam Wiggins, aims to solve common problems that arise when developing software that doesn't consider portability, growth, and maintenance. The concept consists of 12 practices that provide a solid foundation for any internet-based system. These practices include having a single code source with multiple versions, explicitly listing dependencies, and separating configurations from code.
They also involve treating external services as interchangeable, separating build, preparation, and execution stages, and not storing important information within the system. Additionally, the practices recommend that the system should be self-contained, scalable, and able to start and stop quickly. Despite the evolution of tools since its creation, these 12 practices remain relevant.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
