Skip to content

Instantly share code, notes, and snippets.

View ovichowdhury's full-sized avatar
🏠
Working from home

Nahid Chowdhury ovichowdhury

🏠
Working from home
View GitHub Profile
@ovichowdhury
ovichowdhury / introrx.md
Created June 21, 2022 05:52 — forked from staltz/introrx.md
The introduction to Reactive Programming you've been missing

Open an ssl connection to site

openssl s_client -connect client-cert-missing.badssl.com:443

returns

.
.
.
---
@ovichowdhury
ovichowdhury / Guide on Microservices: Backups and Consistency.md
Created May 11, 2021 09:22 — forked from dhana-git/Guide on Microservices: Backups and Consistency.md
Guide on Microservices: Backups and Consistency | Consistent Disaster Recovery for Microservices - the BAC Theorem

Guide on Microservices: Backups and Consistency | Consistent Disaster Recovery for Microservices - the BAC Theorem


The BAC (Backup Availability Consistency) Theorem

When backing up an entire microservices architecture, it is not possible to have both availability and consistency.

  • Eventual Inconsistency with Full Availability (High Availability)
    • When making an independent backup of the state (the event log) of each service, it is possible that one service will be backed up before the event is added to the log, while the other service will be backed up after the corresponding event is added to its log. When restoring the services from backup, only one of the two services will recover its complete log. The global state of the microservice architecture will thus become inconsistent after restoring it from backup.
    • Possible problems,
  • Broken link