How ds-1090/ezyaid works
Project type and purpose
• This is a full-stack mobile application with:
• A Flutter-based frontend targeting Android and iOS
• A Django REST API backend (“eamiddleware”)
• A Kafka consumer service in Python
• A Spark data-processing component
• A Redis configuration (redis.conf) and a Docker Compose setup for orchestration
• Judging by file names (schemes, favorites, registration, notifications), the app appears to list and manage public schemes or resources.
File structure
• Top-level:
• docker-compose.yaml: multi-container orchestration
• requirements.txt: shared Python dependencies
• redis.conf: custom Redis settings
• spark_processing/: one-off or scheduled Spark batch job
• backend/:
• eamiddleware/: Django project
– settings.py, wsgi.py, asgi.py
– models.py, serializers.py, views.py, urls.py
– db.sqlite3: development database
– Dockerfile, requirements.txt
• kafkaconsumer/: lightweight Python service consuming Kafka topics
– kafkaconsumer.py, Dockerfile
• frontend/:
• Flutter project with lib/ (Dart UI pages, state providers)
• android/ and ios/ native wrappers
• pubspec.yaml, test/ widget_test.dart
README for additional insights
• README.md is empty, but file names imply:
• The Django API exposes endpoints for schemes, profiles, favorites, notifications
• Kafka consumer reacts to events (e.g., new registrations)
• Spark job processes an Excel file into a target store (possibly initial data ingestion)