#architecture

AWS framework with six pillars of best practices for designing and operating reliable, secure, efficient, and cost-effective cloud systems.

Pattern where each client type (web, mobile, IoT) has its own dedicated backend adapting microservice APIs to that client's specific needs.

Pattern separating read and write operations into distinct models, optimizing each independently for performance and scalability.

Software design approach centering development on the business domain, using a ubiquitous language shared between developers and domain experts.

Pattern where application state is derived from an immutable sequence of events, providing complete audit trail and the ability to reconstruct state at any point in time.

Architectural pattern where components communicate through asynchronous events, enabling decoupled, scalable, and reactive systems.

Architectural pattern isolating business logic from the outside world through ports and adapters, facilitating testing and technology changes.

Demonstration of dual-interface architecture where the same business logic serves both a traditional web application and an MCP server for AI tools.

Architectural pattern extending microservices to the frontend, allowing independent teams to develop and deploy parts of a web application autonomously.

Architectural style structuring an application as a collection of small, independent, deployable services, each with its own business logic and data.

Code organization strategy where multiple projects coexist in a single repository, sharing dependencies, configuration, and build tooling.

Slidev presentation on 10 reasons to adopt a serverless-first architecture. Deployed on GitHub Pages.

Incremental migration strategy that gradually replaces a legacy system with new components, progressively routing traffic until the old system can be retired.

Twelve-principle methodology for building modern SaaS applications that are portable, scalable, and deployable on cloud platforms.