- Published on
Learn UML Sequence Diagrams with simple examples. Understand how object interactions and messages are represented over time. Explore their structure, use cases, and how they model system logic.
All Posts
All Posts
- system-design (114)
- database (27)
- low-level-design (22)
- oop (15)
- databases (15)
- misc (10)
- normalization (9)
- load-balacing (9)
- indexes (8)
- erd (7)
- caching (7)
- networking (7)
- uml (6)
- solid (6)
- messaging (6)
- security (6)
- theorem (6)
- oop-pillars (5)
- data-partitioning (5)
- data-modeling (4)
- functional-dependency (4)
- bloom-filters (4)
- cdn (4)
- dbms (3)
- relational-data-model (3)
- api-gateway (3)
- recovery (3)
- distributed-file-system (3)
- dns (3)
- proxy (3)
- replication (3)
- data-structures (2)
- interview-prep (2)
- relational-model (2)
- oop-principle (2)
- scalability (2)
- check-sum (2)
- redundancy (2)
- key-concepts (1)
- tips (1)
- armstrong-axioms (1)
- integrity-constraints (1)
- er-diagram (1)
- oop-relationship (1)
- concurrency (1)
- high-availability (1)
- availability (1)
- observability (1)
- monitoring (1)
- error-handling (1)
- leader-follower (1)
- architectural-pattern (1)
- load-balacing-algorithms (1)
- load-balacing-uses (1)
- batch-processing (1)
- streams (1)
- heart-beat (1)
- synchronous (1)
- asynchronous (1)
- quorum (1)
- Published on
Learn what UML (Unified Modeling Language) is, its benefits, and types of diagrams like Use Case, Class, Sequence & Activity. Understand how UML helps design object-oriented systems clearly.- Published on
Learn what a Use Case Diagram is in UML. Understand its purpose, components like actors, use cases, system boundaries, include/extend relationships, and see real-world examples like online shopping.- Published on
Learn why grouping code by feature instead of technical layers (controllers, services, repositories) improves scalability, maintainability, and developer experience in modern software architecture.- Published on
An Orchestrator is a class (or module) responsible for coordinating multiple responsibilities by delegating tasks to other services or components. It does not implement logic itself — it uses others to get the job done.