How ase-fs25/dailygrind works
Project type & purpose
• DailyGrind is a cloud-native, full-stack social-learning application. It consists of:
• A React/Vite frontend that users load in a browser
• Three primary Spring Boot microservices (User, Post, Push-Notification)
• A set of AWS Lambda functions for scheduled and event-driven push notifications and email confirmations
• AWS resources (DynamoDB, SNS/SQS, Cognito, API Gateway/ALB, S3) all provisioned via Terraform
• A Docker-Compose/LocalStack setup for local development
• Prometheus/Grafana monitoring and a fully automated GitHub Actions CI/CD pipeline
File-structure driven architecture
• Top-level folders:
• /frontend → React SPA
• /microservices → three separate Spring Boot services (user-service, post-service, push-notification-service) each with its own Dockerfile, entrypoint, docs, Maven config
• /lambda-functions → lightweight Node.js/Python lambdas for push-notification, scheduler, user-confirmation
• /terraform → IaC modules for network, ECS, Lambda, DynamoDB, SNS/SQS, Cognito, API Gateway, ALB, S3, etc.
• /docker-compose.yaml & Dockerfiles → orchestrate LocalStack, Terraform runner, microservices, frontend, Mailhog
• /prometheus → scrape config for monitoring
Key insights from README
• Single-table DynamoDB design, asynchronous event bus (SNS topics + SQS queues), Cognito for auth, API Gateway/ALB fronting microservices, S3 bucket for hosting frontend, scheduled and event-driven lambdas for push messages, full Terraform provisioning, LocalStack for emulation, GitHub Actions for CI/CD, Prometheus/Grafana observability.