Java Spring Boot Microservices Developer
Budget: ₹37,500 – ₹75,000 INR
I’m building a back-end platform in Java that relies on Spring Boot and a fully event-driven microservices architecture. Every service publishes and consumes events through our internal broker, so the code must be cleanly decoupled and highly testable.
Data persistence will live in MySQL, so each service should expose its own schema and handle migrations automatically. For cloud resources I already have an AWS account configured; the main integration you’ll work with is Amazon S3 for object storage (user uploads, logs, and occasional data exports).
What I need from you is a set of production-ready microservices together with the infrastructure scripts that allow me to spin up the environment quickly.
Deliverables
• Source code for each Spring Boot microservice, wired for event publishing/consumption
• MySQL schema definitions and migration scripts
• S3 integration module with a small demo endpoint showing file upload/download
• Dockerfile and docker-compose (or equivalent) so the whole stack boots locally
Once merged, I’ll run integration tests to confirm:
– Events flow without blocking or data loss
– All REST endpoints respond within agreed latencies
– Services start cleanly from a fresh database using your migration scripts
– S3 operations succeed with temporary credentials
If this sounds like a challenge you enjoy, let’s get started.
Data persistence will live in MySQL, so each service should expose its own schema and handle migrations automatically. For cloud resources I already have an AWS account configured; the main integration you’ll work with is Amazon S3 for object storage (user uploads, logs, and occasional data exports).
What I need from you is a set of production-ready microservices together with the infrastructure scripts that allow me to spin up the environment quickly.
Deliverables
• Source code for each Spring Boot microservice, wired for event publishing/consumption
• MySQL schema definitions and migration scripts
• S3 integration module with a small demo endpoint showing file upload/download
• Dockerfile and docker-compose (or equivalent) so the whole stack boots locally
Once merged, I’ll run integration tests to confirm:
– Events flow without blocking or data loss
– All REST endpoints respond within agreed latencies
– Services start cleanly from a fresh database using your migration scripts
– S3 operations succeed with temporary credentials
If this sounds like a challenge you enjoy, let’s get started.