Tutorial
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?
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
author
author
author
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!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Good
hello
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