Weaponizing SSO for profit - Raz Blog
Introducing the Model Context Protocol \ Anthropic
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to the systems where data lives, including content repositories, business tools, and development environments. Its aim is to help frontier models produce better, more relevant responses.
Authentication: Architecture and Security
Authentication is the foundation of all web services and must be a top priority in terms of security, feature completeness, and UX.
Glassdb: transactional object storage
I was frustrated by the gap between stateless and stateful applications in the
cloud. While I could easily spin up a stateless application as a “serverless”
function in any major cloud provider and pretty much forget about it, persisting
data between requests was a game of pick two among three: cheap, strongly
consistent, portable.
Could I solve portability and lack of transactions myself with a single
client-side solution? I thought it would be possible through object storage
(e.g. AWS S3), which is strongly consistent,
ubiquitous and cheap.
Designing service discovery and load balancing in a microservices architecture | Cerbos
Explore how service discovery and load balancing play crucial roles in microservices for dynamic communication and connection between multiple services.
Top 10 Rules of Continuous Integration - Semaphore
This article provides ten essential rules to optimize your CI pipeline for efficiency, reliability, and code quality.
Flexible Chips Enable the Internet of Everything (IoE)
To realize the Internet of Everything (IoE) revolution, enterprises must be able to deploy item-level intelligence at scale. Flexible chips are the key.
Hyperproperties
One tier worse than regular properties.
Hypermodeling Hyperproperties
When we design programs, we usually look for two kinds of properties: that “bad things” never happen and that “good things” are guaranteed to happen. These are called safety and liveness properties, respectively. These are properties that we want to hold true for every possible program behavior. “We always complete every request” is a liveness property. If our system has it, every program trace will complete every request. If it doesn’t hold, I can give you a example behavior where the server never responds.
Using SPM for declaring a local graph - General - Tuist Community
I’ve noticed some confusion about using SPM to model graphs with local packages, so I wanted to shed some light on the topic. While SPM can describe a project graph, we believe it’s not the best tool for the job—at least not today. SPM’s design decisions make sense in the context of package resolution, but they fall short when it comes to project management. If you want full control over your graph and the developer experience within your project, we recommend limiting SPM to its core purpose: ...
Zero Disk Architecture - blag
State is pain. The next generation of infrastructure tools will be built on diskless paradigm. In this short post I will explain what is Diskless / Zero Disk Architecture
owl-lisp / owl · GitLab
A functional Scheme for world domination
PRQL
PRQL is a modern language for transforming data
How decentralized is Bluesky really? -- Dustycloud Brainstorms
Testing with Go and PostgreSQL: ephemeral DBs
Let’s say you created a Go program that stores data in PostgreSQL — you installed PostgreSQL, wrote the Go code, and everything works; great!
But after writing a test for your code, you wonder: how do you best provide PostgreSQL to your automated tests?
Using gRPC for (local) inter-process communication | F. Werner’s Research Page
Using a full-featured RPC framework for IPC seems like overkill when the processes run on the same machine. However, if your project anyway exposes RPCs for public APIs or would benefit from a schema-based serialisation layer it makes sense to use only one tool that combines these—also for IPC.
Microservices for beginners For the FlashCam software running on the DAQ servers we converged on the following high-level architecture:
Each bright box corresponds to a software process running on the DAQ server.
How Databases Avoid Data Loss with Write-Ahead Logs?
Understanding Database Failure Handling Using Write-Ahead Logs
April King — Refresh vs. Long-lived Access Tokens
Refresh vs. Long-lived Access Tokens
Digital signatures and how to avoid them
Wikipedia’s definition of a digital signature is: A digital signature is a mathematical scheme for verifying the authenticity of digital messages or documents. A valid digital signature on a messag…
What's so bad about sidecars, anyway? | Cerbos
Explore the benefits and limitations of using the sidecar design pattern and the specific use cases where it is most appropriate. Learn how to determine whether a sidecar is a suitable choice for a particular scenario, as well as how to implement sidecars to maximize their benefits.
slash pages
A guide to common pages you can add to your website
Home | Infinigen
Description will go into a meta tag in head /
Alloytools
Reading the Generalized Isolation Level Definitions paper with Alloy
My last few blog posts have been about how I used TLA+ to gain a better understanding of database transaction consistency models. This post will be in the same spirit, but I’ll be using a dif…
Fedi Moderation Tooling Research
System Design Part 1: Setup a Simple Load Balancer using Python - Conrad's Blog - Insights on Technology Leadership and Software Engineering
Unlock the fundamentals of system design with our guide to building a load balancer. Learn how load balancing distributes traffic, optimizes resources, and enhances application reliability by providing redundancy and handling high traffic efficiently
How some of the world's most brilliant computer scientists got password policies so wrong
The US government’s latest recommendations acknowledge that password composition and reset rules are not just annoying, but counterproductive.
The story of why password rules were recommended and enforced without scientific evidence since their invention in 1979 is a story of brilliant people, at the very top of their field, whose well-intentioned recommendations led to decades of ignorance. These mistakes are worth studying, in part, because the people making them were so damn brilliant and the consequences were so long lasting.
Fruits & Roots
The forest offers much but demands much too
Design discussion - Ecto is your application - Chat / Discussions - Elixir Programming Language Forum
Hello, everyone! This should probably be a blog post, but I don’t have a blog, so here we go 😄 My thoughts and frustrations regarding domain modeling in the face of persistence, distilled into a few paragraphs. I’m interested in your opinions. This is probably going to get a bit philosophical, but hopefully also stay practical. I’d like to talk about the age old problem of ORMs. And when it comes to the impedance mismatch problem, Ecto is in the exact same situation as any other ORM in ot...
Revisiting the Outbox Pattern
Comparing the outbox pattern to alternatives like “listen-to-yourself” and 2-phase commit (2PC) transactions. What’s the best choice for data exchange flows between microservices?