@russembkenya Oh, that's funny, I saw the same graphics the other day, except it was with the russian journalists and political opponents you killed or put in jail. I guess you must be russophobe too!
To keep myself accountable whilst building @audiqa_app in public, I' going to regularly write about it. Good thing there's a lot to share and the very first post about its #DesignPhilosophy is now out. Let me know what you think, happy to discuss the process altogether.
@alexjubelin En revanche, avez vous prévu de dédier un épisode au podcast "the wargame"? 1 point qui m'a marqué: pendant tout l'épisode 1 l'équipe bleue ne fait que subir et répondre symboliquement. Limite de l'exercice ou signe qu'on est encore paralysé à l'idée de provoquer la Russie ?
@LeRubicon_org@alexjubelin Donc si je résume: un coup de com qui ne coûte pas bien cher, en partie organisé par des pieds nickelés, et l'intérêt de Trump serait de ne pas aller plus loin. Seulement voilà, l'argument de la rationalité, on le tenait déjà au sujet de Poutine vis a vis de l'Ukraine…
"Awesome Event-Driven Architecture"
This looks very useful: a curated list of articles and resources to learn about EDA, by Lutz Hühnken.
https://t.co/i5opi7VVc9
10 months ago, I created a System Design repo on Github, and I'm excited to share that it recently reached over 15,000 stars.
Thanks to everyone who has starred or forked this repository!
The repository contains a collection of resources to study:
- System Design concepts and building blocks
- Most common tradeoffs
- Around 50 interview problems categorized by difficulty level
- Books/channels to learn more about System Design
I recently made it more structured, added new articles and updated some of the existing articles.
My goal with this repo is to curate the best resources to learn System Design and prepare for interviews.
If you find it valuable, consider giving it a star.
Check it out here: https://t.co/pkVpi6L03n
Each Postgres server can host multiple databases, but be careful! An important note is all databases on the same server share the Write-Ahead Log (WAL).
This means if you perform a point-in-time recovery or rollback, it must be done for all databases on the server. So you cannot selectively restore a single database. If one database becomes corrupted and requires a rollback, you'll need to restore all other databases on that server to the same point. This can be especially problematic when separate (micro-) services manage different databases.
Therefore, if you have multiple loosely coupled services each connecting to a separate database, it's better to put them on different Postgres database servers.