feat: Add Unified Ingestion Architecture Diagram and Flow Design (#99)#101
Open
23shivay wants to merge 1 commit intoArgusoftOpen:mainfrom
Open
feat: Add Unified Ingestion Architecture Diagram and Flow Design (#99)#10123shivay wants to merge 1 commit intoArgusoftOpen:mainfrom
23shivay wants to merge 1 commit intoArgusoftOpen:mainfrom
Conversation
23shivay
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses Task #99: Design Architecture for Unified, Fault-Tolerant Data Ingestion Layer by providing a detailed high-level architecture for real-time and batch ingestion. The submission includes an updated architecture diagram and accompanying notes that outline the ingestion flow, core components, and technology choices.
Key Additions
Architecture Diagram
Added
unified_ingestion_arch_v2.jpgtodocs/images/, capturing the complete ingestion pipeline.Documentation
Added
unified_ingestion_architecture.mdtodocs/, explaining the components, flow, and design rationale.Highlights
Real-Time Ingestion
Redis Pub/Sub layer supports real-time event flow via WebSockets.
Kafka used for high-throughput, durable message queuing.
Batch Ingestion
Redis Streams + worker consumers pull data from APIs, mobile apps, and web portals.
Supports scheduled batch jobs and bulk payload processing.
Storage
PostgreSQL as the persistent, relational data store.
Design Goals Addressed
cc @mvadodariya