System Architecture

Discover the power of domain modeling and exploratory programming in software development. Learn how iterative visual approaches can enhance your understand

Read the original article on packagemain.tech

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…

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.

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.

If you don't know what it operates on or produces, then it operates on or produces itself.

Diagrams should be effortless to create and update, ensuring everyone has access to the latest information.

Read the original article on packagemain.tech

D-Lib Magazine

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.

TL;DR: A world first reverse engineering analysis of AWS Session Tokens. Prior to our research these tokens were a complete black box…

Navigating New Constraints, Requirements, and Capabilities

Cris’ Image Analysis Blog: theory, methods, algorithms, applications

Storage-compute disaggregation in databases has emerged as a pivotal architecture in cloud environments, as evidenced by Amazon ( Aurora ), ...

Dimensions and use of popular paper sizes such as the ISO, SRA, metric or British and American formats

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.

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.

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!

No More Blue Fridays: How eBPF is already being adopted to prevent kernel crashes.

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]

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.

PLDB: a Programming Language Database. Build the next great programming language.