bcarlin/bcarlin.net
1
0
Fork 0
Code Pull requests Activity Actions

fix: typos

Browse source
This commit is contained in:
Bruno Carlin 2025-06-16 02:58:41 +02:00
parent e4a5029d24
commit db00d19d7f
WARNING! Although there is a key with this ID in the database it does not verify this commit! This commit is SUSPICIOUS.
GPG key ID: 8E254EA0FFEB9B6D
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/blog/007-prepare-for-the-next-internet-outage.md
View file

@ -49,8 +49,8 @@ least one of these vendors.
product? Is your app deployed with a Github Action ? The more you know, the
more you’re prepared.
* *Vendor Due Diligence*: Uptime guarantees (3? 4? 5 nines?) are just marketing.
Take it as such. What is your vendor’s architecture? its Continuity plan? Its
transparency on incidents? those are far more important criteria.
Take it as such. What is your vendor’s architecture? Its continuity plan? Its
transparency on incidents? Those are far more important criteria.
* *Consider Multi-Cloud Strategies*: You would not put all your servers in the
same datacenter? Then do not put all your infrastructure in the same IaaS
provider! (If you would, you should do something about it!)
@ -112,7 +112,7 @@ some that will affect your business.
Be prepared:
* Know your infrastructure, your vendors, their vendors, etc.
* Asses risks on a regular basis. Your app evolves, your vendors too. What is
* Assess risks on a regular basis. Your app evolves, your vendors too. What is
true at one moment is not at the next.
* Plan for the worst case. Incidents will happen. Your job is to make it so that
the user experience is not impacted.