Jarxi

[Version 2] The Pull Model Inverts a Rollout Pipeline

Flux didn't replace our hand-written rollout pipeline. It inverted one hop: CI stopped applying to the cluster and started opening a pull request instead.

Version 1 was a push system. A state machine in a service, one CI job per step, SSH to the machines. The engine decided, the runner acted, and the cluster found out afterwards. Then one of our clus......

Posted by Jessie Jia on 2026-10-17

Technical Architecture MLOps

[Version 1] A Hand-Written Model Rollout Pipeline

A new model recipe lands in the repo and the rollout starts itself. One engine owns the state machine and the traffic APIs; one CI job per step owns the machines over SSH. Every forward step has a backward step.

This is version 1 of our model rollout pipeline. Nothing clever: no orchestration framework, no operator, no CRDs. A state machine in a service, a single CI workflow, and SSH. Writing it down becau......

Posted by Jessie Jia on 2026-10-08

Technical Architecture MLOps

One API Client, Two Authentication Channels

The web uses an HTTP-only cookie, the CLI uses a bearer token. The server checks both in one middleware, and each shell injects its own way of producing credentials — so feature code never learns which platform it is on.

Following on from the previous post: three shells sharing one set of logic packages. What about auth? The web wants an HTTP-only cookie — sent automatically, unreadable from JS, safe against XSS. T......

Posted by Jessie Jia on 2026-09-24

Technical Architecture Auth

Next.js Is Just a Shell, Peer to Electron

The easiest mistake in a multi-client monorepo is treating the Next.js app as the product and everything else as a port. Demote it to a shell and the package boundaries fall out — especially the one the CLI forces on you.

Say a product needs a web app, a desktop app and a CLI. The obvious path is to build the Next.js app first, then find a way to stuff it into Electron, then find something for the CLI to reuse. That......

Posted by Jessie Jia on 2026-09-24

Technical Architecture Monorepo

Cross-Package Imports Are Type-Only, Runtime Goes Through ctx

import type compiles to nothing, so it creates no runtime dependency edge. That is how dozens of UI packages can know each other's types while never loading each other — the plugin boundary lives in one keyword.

I was reading an “everything is a plugin” frontend codebase — dozens of UI packages that almost never import each other. One package opened with these two lines: 12import type { Context }......

Posted by Jessie Jia on 2026-09-24

Technical TypeScript Architecture

Judge Your Judge Twice Before You Trust It

I used a large model as a judge to fact-check SFT data. Judging the same note twice gave zero errors on one run and a dozen on the next. A single verdict is a coin flip.

I have been turning a batch of meeting transcripts into SFT data, so a small model can write meeting notes against a fixed template. After the pipeline was running and the filters were written, I c......

Posted by Jessie Jia on 2026-09-22

Technical AI SFT Data

Prometheus Behind NAT: Scraping Without Open Ports

How a pull-based monitor reaches a machine with no public IP. The tunnel is a phone line, not a mailbox — and nothing exists until someone asks for it.

Prometheus pulls. It sends an HTTP GET to your machine and reads the response. Simple — until your machines sit in private subnets across three clouds, with no public IPs and security groups you’d ......

Posted by Jessie Jia on 2026-08-25

Technical Prometheus Monitoring Networking

Load Leveling vs Load Balancing: The Fan-Out Pattern

Two queues, one event. Load balancing splits work across identical workers. Load leveling spreads work across time, so a slow consumer never blocks a fast one.

Most queue diagrams look the same: one producer, one queue, several workers. The point is to share work out. More workers, more throughput. Then one day you write a system where the same event goes......

Posted by Jessie Jia on 2026-08-25

Technical Architecture System Design Queue

[Version 2] The Pull Model Inverts a Rollout Pipeline

Flux didn't replace our hand-written rollout pipeline. It inverted one hop: CI stopped applying to the cluster and started opening a pull request instead.

[Version 1] A Hand-Written Model Rollout Pipeline

A new model recipe lands in the repo and the rollout starts itself. One engine owns the state machine and the traffic APIs; one CI job per step owns the machines over SSH. Every forward step has a backward step.

One API Client, Two Authentication Channels

The web uses an HTTP-only cookie, the CLI uses a bearer token. The server checks both in one middleware, and each shell injects its own way of producing credentials — so feature code never learns which platform it is on.

Next.js Is Just a Shell, Peer to Electron

The easiest mistake in a multi-client monorepo is treating the Next.js app as the product and everything else as a port. Demote it to a shell and the package boundaries fall out — especially the one the CLI forces on you.

Cross-Package Imports Are Type-Only, Runtime Goes Through ctx

import type compiles to nothing, so it creates no runtime dependency edge. That is how dozens of UI packages can know each other's types while never loading each other — the plugin boundary lives in one keyword.

Judge Your Judge Twice Before You Trust It

I used a large model as a judge to fact-check SFT data. Judging the same note twice gave zero errors on one run and a dozen on the next. A single verdict is a coin flip.

Prometheus Behind NAT: Scraping Without Open Ports

How a pull-based monitor reaches a machine with no public IP. The tunnel is a phone line, not a mailbox — and nothing exists until someone asks for it.

Load Leveling vs Load Balancing: The Fan-Out Pattern

Two queues, one event. Load balancing splits work across identical workers. Load leveling spreads work across time, so a slow consumer never blocks a fast one.

FEATURED TAGS

ABOUT ME

RECENT POSTS

ARCHIVES