System Architecture

System Architecture

7404 bookmarks
Custom sorting
The Architecture of Oban
The Architecture of Oban
Oban is an Elixir job processing system backed by PostgreSQL for persistence and coordination. It stands on the shoulders of giants, blending OTP and Po…
·speakerdeck.com·
The Architecture of Oban
Remove Control Flag Refactoring – How to Simplify Logic
Remove Control Flag Refactoring – How to Simplify Logic
Simplify your code with the remove control flag refactoring technique in C#. See the benefits of removing control flags in this guide to applying the technique.
·devleader.ca·
Remove Control Flag Refactoring – How to Simplify Logic
Taildrop was kind of easy, actually
Taildrop was kind of easy, actually
Taildrop was the first test of an experimental p2p app discovery layer in Tailscale. Let’s talk about why it was so easy to build, and where we go from here.
·tailscale.com·
Taildrop was kind of easy, actually
Software Architecture Diagrams with C4 Model
Software Architecture Diagrams with C4 Model
Diagrams should be effortless to create and update, ensuring everyone has access to the latest information.
·packagemain.tech·
Software Architecture Diagrams with C4 Model
When Objects Are Not Enough
When Objects Are Not Enough
Alan Kay mentions in a talk that the Smalltalk don't scale quite well to big teams and infrastructure. However, he had some ideas on how to make OOP scale.
·tonysm.com·
When Objects Are Not Enough
Revealing the Inner Structure of AWS Session Tokens
Revealing the Inner Structure of AWS Session Tokens
TL;DR: A world first reverse engineering analysis of AWS Session Tokens. Prior to our research these tokens were a complete black box…
·medium.com·
Revealing the Inner Structure of AWS Session Tokens
#12 Document It: Architecture Decision Log
#12 Document It: Architecture Decision Log
Capturing and storing architectural decisions can simplify the lives of future team members. We can keep a historical record of why certain architectural choices were made and at what time.
·newsletter.fractionalarchitect.io·
#12 Document It: Architecture Decision Log
Many yes/no attributes: table design study
Many yes/no attributes: table design study
Author: Alexey Makhotkin squadette@gmail.com. I wanted to demonstrate the relationship between the logical model and a physical model. We’re going to design a commonly seen use case: many yes/no attributes of a single anchor (in our case, Restaurant). Then we’ll discuss how the physical tables would be designed. We’ll see that sometimes physical design strategy changes as the system becomes more mature. At the same time, logical design elements never change if the business requirement is still relevant.
·kb.databasedesignbook.com·
Many yes/no attributes: table design study
Igniter - Rethinking code generation with project patching
Igniter - Rethinking code generation with project patching
Ash Framework is ~4 years old, and we’ve only *just now* introduced generators and installers. As of Ash 3.1, we’ve now got generators and installers, thanks to our latest project [Igniter](https://hexdocs.pm/igniter)! First, we’ll cover why *I avoided them for so long*. Then we dive into how Igniter changes the game!
·alembic.com.au·
Igniter - Rethinking code generation with project patching
No More Blue Fridays
No More Blue Fridays
No More Blue Fridays: How eBPF is already being adopted to prevent kernel crashes.
·brendangregg.com·
No More Blue Fridays
Log-structured file system - Wikipedia
Log-structured file system - Wikipedia
A log-structured filesystem is a file system in which data and metadata are written sequentially to a circular buffer, called a log. The design was first proposed in 1988 by John K. Ousterhout and Fred Douglis and first implemented in 1992 by Ousterhout and Mendel Rosenblum for the Unix-like Sprite distributed operating system.[1]
·en.wikipedia.org·
Log-structured file system - Wikipedia
Sprite (operating system) - Wikipedia
Sprite (operating system) - Wikipedia
Sprite is an experimental Unix-like distributed operating system developed at the University of California, Berkeley by John Ousterhout's research group between 1984 and 1992. Its notable features include support for single system image on computer clusters[1] and the introduction of the log-structured file system. The Tcl scripting language also originated in this project.
·en.wikipedia.org·
Sprite (operating system) - Wikipedia
Reflections on Declarative Configuration
Reflections on Declarative Configuration
Advantages and pitfalls of Infrastructure as Code, and the distinction between IaC and Declarative Configuration.
·itnext.io·
Reflections on Declarative Configuration