Published Oct 22, 2015

The Twelve-Factor App: Backing Services, Building and Releasing, Stateless Processes

    Explore the Twelve-Factor App methodology, focusing on backing services, stateless processes, and the nuanced build-release-run cycle, while Humor meets insight as the complexity of JS libraries and Git tips are dissected with wit.
    Episode Highlights
    Coding Blocks logo

    Popular Clips

    Episode Highlights

    • Configuration

      Configuration strategies for backing services are crucial in the Twelve-Factor App principles. Alan Underwood and Michael Outlaw emphasize that changes to these services should only require configuration adjustments, not code redeployment. This approach allows for seamless transitions between resources, such as switching databases, without altering the application's code 1. Outlaw notes that logs and data should be treated as independent resources, accessed through configuration-stored credentials 2. Underwood adds, "If you have to redeploy your code simply to change a connection, then you violated this number four backing service."

         

      Importance

      The importance of backing services is rated highly in the Twelve-Factor App methodology. Joe Zack and Michael Outlaw agree that the ability to change service connections without recompiling is essential for efficient app management 3. Despite some discrepancies in importance ratings between configurations and backing services, the consensus is that both are critical 4. Underwood asserts, "Backing services should be decoupled as much as possible."

    Related Episodes