It's just fascinating. How is modern software designed? 🤔 Some design-level considerations for scalability, maintainability eventual consistency, availability & reliability. 👨‍💻 Interview Prep. 👨‍💻

This repo contains a sample application based on a Garage Management System for Pitstop - a fictitious garage. The primary goal of this sample is to demonstrate several software-architecture concepts like: Microservices, CQRS, Event Sourcing, Domain Driven Design (DDD), Eventual Consistency.

Storage for private, distributed, offline-first applications.

An example of Choreography-based sagas in Spring Boot/JPA microservices

CQRS, using Clean Architecture, multiple databases and Eventual Consistency

CRDT Tutorial for Beginners (a digestible explanation with less math!)

Reliable eventual consistency for Microservices

Software architecture design guidelines for apps running under eventual consistency. Works with domain driven design. Approved by practitioners.

Outbox and Inbox Pattern in .NET (scalability & fault tolerance). Ensures eventual consistency between services. (microservices, event-driven architecture, message streaming)

Event Sourcing + CQRS using Golang Tutorial

A collection of Algorithms to Synchronise changes across multiple clients using Operational Transformation

Collaborative and distributed Markdown text editor, started as a bachelor thesis project at HEIG-VD.

Example of a list-making Web API using CQRS, Event Sourcing and DDD.

A web-based board game platform designed for players to connect and play.

Orda: A client and server written in Go. CRDT-based data synchronization supporting document database.

End-to-End Cucumber Tests

Rust implementation of NextGraph, a Decentralized and local-first web 3.0 ecosystem

Real-time message streaming over a Hazelcast in-memory data grid

Simulated e-commerce platform with six microservices, using various technologies such as MongoDB, PostgreSQL, Docker, and DDD.