|
|
|
|
|
by davidfstr
1459 days ago
|
|
> Servers can also be liability. You need to document, implement and maintaing hardening, have a process for regularly patching os and apps, […], have backup and disaster recovery procedures, regularly test the procedures, […] and so on. Much of this complexity I eliminate by using the Immutable Server pattern: Specifically I deploy my app as a Docker container hosted on a virtual machine cluster managed by AWS ElasticBeanstalk. OS upgrades and patches (outside the container) are done by AWS. If anything goes wrong with a VM I just terminate it and a different fresh VM spins up to take its place. |
|
What do you do if you need to launch another instance of the app? For staging or testing.