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

Disclaimer
This guide won’t cover everything, it won’t be a comprehensive guide, and the steps that are shown need to be carefully reviewed and tested in your development/pre-production environment. …


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

Disclaimer
This guide won’t cover everything, it won’t be a comprehensive guide, and the steps that are shown need to be carefully reviewed and tested in your development/pre-production environment. …


This is the fourth 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 2 things:

  • Distributed Storage
  • Backups

Disclaimer
This guide won’t cover everything, it won’t be a comprehensive guide, and the steps that are shown need to be carefully reviewed and tested in your development/pre-production environment. …


This is the third part of the series Save yourself from a disaster: Redundancy on a budget.

How can we make sure our most important asset (which is the DB) is safely secured in case of a disaster?

We could do mainly 2 things (and you better do both of them):

Disclaimer
This guide won’t cover everything, it won’t be a comprehensive guide, and the steps that are shown need to be carefully reviewed and tested in your development/pre-production environment. …


This is the second 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 2 things:

  • Distributed Storage
  • Backups

Disclaimer
This guide won’t cover everything, it won’t be a comprehensive guide, and the steps that are shown need to be carefully reviewed and tested in your development/pre-production environment. …


This is the first part of the series Save yourself from a disaster: Redundancy on a budget.

How can we make sure our most important asset (which is the DB) is safely secured in case of a disaster?

We could do mainly 2 things (and you better do both of them):

  • Backups
  • Redundancy

Disclaimer
This guide won’t cover everything, it won’t be a comprehensive guide, and the steps that are shown need to be carefully reviewed and tested in your development/pre-production environment. …


What can we learn from the latest major cloud incident (ie. burning OVH datacenter)? Do not put all your eggs in one basket!
The only certain thing is that it’s not a matter of IF there’ll be a disaster but rather WHEN, so better be not caught off guard.

Fire at Our Strasbourg Site

I’m running a bunch of very small websites (with very simple infrastructure topology) and I wanted to put in practice something on a budget. So, I’ve decided to go multi-cloud.

Evolution

I’ve started with an infrastructure that looked like this:


LastPass has recently decided to limit their free account to allow only 1 active device (computer or mobile) per account.
In the lights of this debatable decision, many people have decided to move away from it.

https://www.androidauthority.com/lastpass-free-survey-1201723/

You’re not sure which one to use? Have a look at the list here.

So, I’ve decided to move to KeePass:
This time I’ve decided not to give it to the “cloud”. I know, I’ll sacrifice some good features but in exchange, I’ll get it free-forever and 100% control of the data. It comes with plugins as well (need to vet them first!).


There are a lot of definitions floating around, all of them about a special niche type of developer.

10x Developer

(ten eks dɪˈveləpə)
A 10x developer is an individual who is thought to be as productive
as 10 others in his or her field.

Source

Fullstack Developer

(fʊl-stæk dɪˈveləpə)
Someone who can work on both the back-end and front-end of systems.

Source

Ninja Developer

(ˈnɪndʒə dɪˈveləpə)
The Ninja is an expert in a particular programming language, but is
comfortable using any other language.

Source

Rockstar Developer

(rɒk-stɑː dɪˈveləpə) A computer programmer with such strong skills and so much specific experience…


I left Skuola.net as CTO to join Radical (formerly BAGBNB) as Engineer.

TL;DR

I jumped boat, changed role, changed tech stack, I’m enjoying a bit more of tranquillity, I have a bit more family time, I got my (dev) passion back! Way to go folks 😎

Long Story

I’m just sharing some reasons for this decision and few insights on the past few years, for my future self, for the ones who have asked or will ask. Also, for a good DRY approach 🙂

It was a positive experience overall, I did achieve many good things during my tenure as…

Fabio Cicerchia

Passionate Developer with 15+ years in web applications and web portals. Focused on software performance and maintainability. Former CTO, now Engineer @ Radical

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store