Search

Lessons (23)

• Onion Architecture & Clean vs Hexagonal vs Onion

  … All three share the same rule: 🎯 The business logic is at the centre and depends on nothing. Infrastructure …

• Clean Architecture

  Organise an application in layers so business rules don't depend on frameworks, databases or the web. Follow …

• Normalization & Denormalization

  … depend on the whole key Rule: be in 1NF, and every non-key column must depend on the …

• D — Dependency Inversion Principle

  High-level business logic should depend on abstractions, not on concrete details like databases or email providers. The …

• Clean Architecture in Depth

  … and the Dependency Rule](/img/architecture/clean-circles.svg) 📘 The Dependency Rule: source code dependencies must point only …

• Layered (N-Tier) Architecture

  … layered design, the business layer depends on the persistence layer . So business rules end up shaped by database …

• SOLID at a Glance

  … microwave's buttons. D Dependency Inversion Depend on abstractions , not concrete details. Lamps depend on the socket, not …

• Resilience Patterns

  … Fallbacks and graceful degradation When a non-critical dependency fails, degrade instead of erroring: Failed dependency Fallback --- --- Recommendations …

• Hexagonal Architecture (Ports & Adapters)

  … fast and realistic. - Same Dependency Rule as Clean Architecture: nothing in the core imports an adapter.

• React Hooks in Practice

  … When to use each, the rules of hooks, and the mistakes that cause infinite loops. The big idea …

• Choosing an Architecture

  … automated checks for architecture rules (dependency rules, latency budgets) Guard the architecture continuously in CI ADRs for every …

• Microkernel (Plugin) Architecture

  … the only thing plug-ins may depend on Registry Knows which plug-ins exist, their versions, and how …

• Frontend Security

  … your dependencies A typical frontend app has 1,000+ npm packages . One compromised package can steal data from …

• Database Relations & Foreign Keys

  Model one-to-one, one-to-many and many-to-many data with keys, constraints and deletion rules …

• Authentication, Authorization & API Security

  … git - [ ] Security headers ( helmet in Express) - [ ] Dependencies scanned ( npm audit , Dependabot) - [ ] Log security events, but never log passwords …

• REST API Design

  … res.status(201).json(payment); }); Rule 6: Version your API Once clients depend on your API, breaking changes …

• Scaling, Load Balancing & Rate Limiting

  … Design for it: Pattern Purpose --- --- Timeouts Never wait forever on a dependency Retries with exponential backoff + jitter Survive …

• Vertical Slice Architecture & the Modular Monolith

  … queries read directly, commands go through the domain. Rules of thumb Rule Why --- --- Maximise coupling inside a slice …

• React Fundamentals

  … name }) . JSX rules: return one root element (or a fragment < …</ ), use className instead of class , write {expression} for …

• Kafka Producers

  … event ID, type, schema version - [ ] A schema (Avro/Protobuf/JSON Schema) with compatibility rules - [ ] Flush and close the …

• Big-O Notation Made Simple

  … That's why binary search is so fast. The 4 rules for calculating Big-O 1. Drop constants …

• Deploying & Operating Microservices

  … Remember to delete old flags, or they become technical debt. Never break your consumers Other services depend on …

• Helm, kubectl Cheat Sheet & Best Practices

  … team-shop } rules: - apiGroups: [""] resources: ["pods", "pods/log"] verbs: ["get", "list", "watch"] --- apiVersion: rbac.authorization.k8s.io/v1 …