Architecture on Commentary of Takao

Serverless Architecture Patterns: Beyond Lambda Functions

Tue, 17 Sep 2024 00:00:00 +0900

Serverless computing has evolved far beyond replacing simple REST APIs with Lambda functions behind API Gateway. Modern serverless architectures are fully event-driven, asynchronous, and decompose monoliths into coordinated function workflows. Major enterprises now run production workloads on AWS Lambda, Azure Functions, and Cloudflare Workers. This article explores patterns that go beyond the basics.

Event-Driven Architecture Foundation

At the core of serverless is the event-driven model: event producers emit events, event routers deliver them, and event consumers react. AWS offers multiple routing services — EventBridge for schema-aware event buses, SQS for queue-based decoupling, SNS for pub/sub messaging, and Kafka for high-throughput streaming.

TypeScript Project References: Scaling Large Codebases

Tue, 13 Aug 2024 00:00:00 +0900

Introduction

As TypeScript codebases grow, the monolithic tsconfig.json approach breaks down. Every invocation of tsc type-checks and emits the entire project — a process that can take minutes even with --noEmit in large monorepos. Worse, without module boundaries, any file can import any other file, creating tangled dependency graphs that are difficult to refactor. TypeScript Project References solve this by allowing you to split your codebase into independent sub-projects, each with its own tsconfig.json, enabling incremental builds, enforced API boundaries, and dramatically faster type-checking.

CSS @layer: Managing Cascade with Layer Architecture

Tue, 11 Jun 2024 00:00:00 +0900

If you have ever battled specificity wars in a large CSS project — overriding third-party styles, sprinkling !important declarations, or restructuring HTML just to win the cascade — @layer is the solution you have been waiting for. The CSS @layer at-rule gives developers explicit control over the cascade order, independent of specificity or source order.

The Cascade Problem Before @layer

Before @layer, cascade management relied entirely on conventions: BEM naming, SMACSS categories, ITCSS architecture. These conventions worked, but they were not enforced by the browser. Third-party CSS could override carefully crafted component styles, and source-order fragility meant that a single <link> tag reorder could break an entire design system.