Code Archaeology
Author

Code Archaeology

Learn from the past to understand the present

30
Articles
0
Likes
7
Views
0
Comments
Recent Articles

Latest from Code Archaeology

30 recent articles
Code Archaeology
Code Archaeology
Oct 14, 2026 · Backend Development

Evolutionary Architecture Structure: Connascence, Architectural Quanta, and Contract-Driven Design

This article explores how software topology determines evolvability through connascence-based coupling analysis, architectural quanta as independently deployable units, contract spectra from strict RPC to loose key-value, microservices as evolutionary templates, data mesh for analytical data, and evolutionary database practices including Expand/Contract migrations and data governance.

architectural quantumbounded contextconnascence
0 likes · 56 min read
Evolutionary Architecture Structure: Connascence, Architectural Quanta, and Contract-Driven Design
Code Archaeology
Code Archaeology
Sep 28, 2026 · Fundamentals

Beyond Static Structure: C4's Dynamic, Deployment & Landscape Diagrams

This article explains C4 model's three supplementary diagrams—Dynamic, Deployment, and System Landscape—detailing their purpose, scope, notation, and practical examples using an internet banking system to illustrate runtime interactions, multi-environment deployments, and enterprise-wide system relationships.

AWSC4 modelDocker
0 likes · 27 min read
Beyond Static Structure: C4's Dynamic, Deployment & Landscape Diagrams
Code Archaeology
Code Archaeology
Sep 7, 2026 · Fundamentals

Why C4 Starts with System Context Diagrams: A Step-by-Step Guide

This article explains why the C4 model begins with system context diagrams, detailing their purpose, key elements (people, software systems, relationships), notation conventions, and a step-by-step example of creating a context diagram for an online banking system integrating with core banking and email services.

C4 modelarchitecture documentationonline banking example
0 likes · 14 min read
Why C4 Starts with System Context Diagrams: A Step-by-Step Guide
Code Archaeology
Code Archaeology
Sep 2, 2026 · Fundamentals

C4 Model: Four Abstraction Layers for Software Architecture Visualization

This article explains the C4 model's four abstraction layers—Software System, Container, Component, and Code—and their corresponding diagrams, plus three supplementary diagrams, emphasizing that shared abstractions are more critical than unified notation for effective software architecture communication.

C4 modelabstraction layersarchitecture diagrams
0 likes · 10 min read
C4 Model: Four Abstraction Layers for Software Architecture Visualization
Code Archaeology
Code Archaeology
Aug 31, 2026 · Fundamentals

How to Draw Architecture Diagrams: Principles, Tools & Modeling Standards

This article teaches software architects how to create effective architecture diagrams by following representational consistency, avoiding premature tool attachment, selecting tools with layers/templates/magnets, understanding UML/C4/ArchiMate standards, and applying six diagramming conventions for titles, lines, shapes, labels, color, and legends.

ArchiMateC4 modelUML
0 likes · 11 min read
How to Draw Architecture Diagrams: Principles, Tools & Modeling Standards
Code Archaeology
Code Archaeology
Aug 26, 2026 · R&D Management

Architectural Decision Records (ADR): A Practical Framework for Effective Architecture Decisions

This article defines architectural decisions, distinguishes them from technical decisions using architectural significance criteria, outlines three anti-patterns (Covering Your Assets, Groundhog Day, Email-Driven Architecture), and details the ADR framework with its seven sections, storage strategies, and applications for standards and legacy systems.

ADRAnti-PatternsDocumentation
0 likes · 22 min read
Architectural Decision Records (ADR): A Practical Framework for Effective Architecture Decisions
Code Archaeology
Code Archaeology
Aug 24, 2026 · Backend Development

Why Spring Changed HttpMethod from Enum to Class: Fixing an Open Set Mismatch

Spring changed HttpMethod from enum to class in Spring 6.0 because HTTP methods form an open, extensible set per RFC 7231, making enum's closed nature a poor fit that forced workarounds like dual getters and null-returning resolve methods until a major version break allowed the fix.

API DesignEnum vs ClassHTTP Methods
0 likes · 7 min read
Why Spring Changed HttpMethod from Enum to Class: Fixing an Open Set Mismatch