// Tutorial //

Configuration Drift: Phoenix Server vs Snowflake Server Comic

Published on March 26, 2018
Default avatar

By Teddy Hose, Masami Kubo, and Hazel Virdo

Configuration Drift: Phoenix Server vs Snowflake Server Comic

Note: This comic adaptation covers a portion of an article on immutable infrastructure. If you’d like to learn more, we recommend taking a look at the original piece: What Is Immutable Infrastructure?

Phoenix server vs Snowflake Server

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about us

About the authors
Default avatar
Teddy Hose


Default avatar
Masami Kubo


Default avatar
Hazel Virdo


Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

This comment has been deleted

    It’s just a fun way to describe the idea of servers which can be “killed” randomly without worry because your environment is resilient enough to “rise from the ashes” (like the mythical Phoenix) fairly easily, if not automatically. It’s not a specific technology or even a specific technique, but just a general idea of being vigilant about documenting configuration and ensuring that your recovery process is well practiced in an actual production environment. The ultimate “Phoenix server” would be an environment where this process is 100% automated with built-in redundancy across the entire application stack so that any given piece of the infrastructure could be randomly destroyed with zero downtime

    Try DigitalOcean for free

    Click below to sign up and get $200 of credit to try our products over 60 days!

    Sign up