• Save yourself from a disaster #10: Play with Providers

    This is the tenth part of the series Save yourself from a disaster: Redundancy on a budget. Try to experiment and find the right technology.

    /

  • Save yourself from a disaster #9: Disaster Recovery Plan

    This is the ninth part of the series Save yourself from a disaster: Redundancy on a budget. How are you going to behave in the event of a disaster? You’ll start running around waving your hands up in the air? Ok, stop, breathe, and try to follow these advices.

    /

  • Save yourself from a disaster #8: Manual Configurations

    This is the eighth part of the series Save yourself from a disaster: Redundancy on a budget. Snowflakes servers are our enemies, we should avoid them like the plague. Our best allied are fail-proof reproducible steps, even better if coded in an actionable code, like Infrastructure as Code. We went through many steps, are you […]

    /

  • Save yourself from a disaster #7: Billing Impact

    This is the seventh part of the series Save yourself from a disaster: Redundancy on a budget. In this post we will check about the “hardest” part of all of it, the money coming out of our pockets. So, let’s crunch some numbers.

    /

  • Save yourself from a disaster #6: Redundancy of DNS

    This is the sixth part of the series Save yourself from a disaster: Redundancy on a budget. How can we make sure our website is always available and not going down when a node is offline? We could do mainly 2 things: Secondary DNS Manual Switch

    /

  • Save yourself from a disaster #5: Redundancy of Web Servers

    This is the fifth part of the series Save yourself from a disaster: Redundancy on a budget. How can we make sure our second most important asset is safely secured in case of a disaster? We could mainly 3 things: Duplicate VM Docker Kubernetes

    /