How mohammadalqaisyyy/decentralized_cluster-based_nosql_db_system works
Project type and purpose
• This is a distributed, cluster-based NoSQL database system composed of multiple Spring-Boot microservices running in Docker containers.
• Purpose: demonstrate a decentralized database where each node stores JSON documents on its filesystem and coordinates reads/writes via REST and Kafka messaging to improve throughput and security.
File structure
• Top-level directories (services)
• BootstrapNode – the “seed” service that tracks cluster membership and responds to client bootstrap requests
• node_1, node_2, … node_5 – five identical data-store nodes, each running its own Spring Boot application, local JSON file store, and Kafka producer/consumer
• demo – a web-app client (JSP front end + Spring MVC controllers) illustrating login and CRUD against the cluster
• docker-compose.yml – orchestrates all services (BootstrapNode, node services, demo app, plus Kafka broker/container)
• Key packages under each node_x:
• config – Spring Security, RSA key props, RestTemplate, Kafka producer/consumer setup
• controller – REST endpoints for auth, bootstrap, client queries, node info
• databaseManager – file-based DB handler, collections, documents, index updaters
• redirection – broadcastQuery and affinity-based routing of operations
• commands – handlers for database/collection/document operations
• Resources: application.properties, certs (public/private PEM), under-resource DB folders containing JSON files + index files.
README for additional insights
• Confirms Java+Spring, Docker, and Kafka usage
• Emphasis on multi-node architecture for speed and security
Elements
• Containers (rectangles) for: Demo App, BootstrapNode, Node_1…Node_5, Kafka Broker
• Blue for web tier (Demo front end)
• Green for control plane (Bootstrap)
• Orange for data nodes
• Yellow for messaging layer (Kafka)
• Ports/endpoints where relevant (e.g., 8080 REST, 9092 Kafka)
Detail
• Call out index files under each node for quick lookups
• Certificate files feeding into Spring Security for each node
• Both synchronous (REST) and asynchronous (Kafka) flows