AWS Builder Center
Building FarmMitra: My Journey journey with AWS Lead

Building FarmMitra: My Journey journey with AWS Lead

FarmMitra is an AWS-powered digital marketplace that connects farmers with buyers across India. Farmers can list their crops, buyers can discover listings and make offers, and farmers can compare offers before connecting with the right buyer. The platform uses AWS Lambda, API Gateway, DynamoDB, and AWS Amplify to provide a scalable serverless architecture.

Building FarmMitra: My Journey as Team Captain and AWS Lead

Turning a Problem Into a Working AWS Application

During the Bharat Builds hackathon, our team decided to build FarmMitra, a marketplace designed to connect farmers with buyers beyond their local markets.
The core idea was simple:
LIST → DISCOVER → OFFER → COMPARE → CONNECT
Farmers can list their crops, buyers can discover available crops and make offers, and farmers can compare those offers before connecting with a buyer.
While the team worked on different parts of the application, I took responsibility for the overall technical direction as the Team Captain / Full-Stack & AWS Lead.



My Role in FarmMitra

My main responsibilities included:
  • Designing the application architecture
  • Leading overall development and integration
  • Developing backend APIs
  • Integrating AWS services
  • Connecting DynamoDB for data storage
  • Deploying the application using AWS Amplify
  • Managing the GitHub repository
  • Handling final integration and deployment
My focus was making sure the different parts of FarmMitra worked together as one application.



Designing the Architecture

Before building the backend, I defined how the main components would communicate.
For our MVP, we followed a serverless architecture using AWS:
Frontend → API Gateway → Lambda → DynamoDB
The frontend communicates with our APIs through Amazon API Gateway.
API Gateway invokes the required AWS Lambda function, which handles the application logic and communicates with Amazon DynamoDB.
This allowed us to build the backend without managing traditional servers.



Building the Backend

One of my primary responsibilities was developing the backend APIs using AWS Lambda and API Gateway.
The APIs handled the core marketplace operations, including working with crop listings and retrieving marketplace data.
For example, when a farmer submits a crop listing:
Farmer → Frontend → API Gateway → Lambda → DynamoDB
The request is processed by Lambda and the required information is stored in DynamoDB.
The response is then returned to the frontend so the user can see the updated information.



DynamoDB Integration

We used Amazon DynamoDB as the application's data storage layer.
The database supported the information required for our MVP, such as crop listings and marketplace data.
Instead of building an unnecessarily complicated database structure, we focused on the data needed to demonstrate the complete FarmMitra workflow.
This helped us keep the MVP simple while still having a functional cloud backend.



Connecting Everything Together

One of my biggest responsibilities was integration.
Building a frontend, backend, and database separately is one thing. Making them work together reliably is another.
I worked on connecting the frontend with our APIs, making sure requests reached the correct Lambda functions, and ensuring the backend could correctly interact with DynamoDB.
This integration turned separate components into a complete application.



Deployment With AWS Amplify

After development and integration, I handled the final deployment using AWS Amplify.
Moving from local development to a cloud deployment introduced several practical challenges around configuration, API connectivity, builds, and AWS resources.
Working through these issues gave me valuable hands-on experience with deploying a real application rather than simply running it locally.
Our development flow became:
GitHub → AWS Amplify → Deployed FarmMitra Application



Managing the Team and Repository

As Team Captain, I was also responsible for keeping the development process coordinated.
I managed the GitHub repository and worked on integrating contributions from different parts of the team.
The goal was to make sure everyone could work on their responsibilities while the final application remained consistent and deployable.
This taught me that technical leadership isn't only about writing code. It also involves making architectural decisions, solving integration problems, and keeping the entire system moving toward the final goal.



What I Learned

FarmMitra gave me practical experience across the complete development lifecycle:
Idea → Architecture → Backend → Database → Integration → AWS → Deployment
More importantly, I learned that building a product is not just about knowing individual technologies.
You need to understand how those technologies connect and how a user's action travels through the entire system.
As the Team Captain and AWS Lead, FarmMitra gave me an opportunity to work with AWS Lambda, API Gateway, DynamoDB, Amplify, GitHub, backend APIs, and application architecture while working toward a real-world problem.



Final Thoughts

FarmMitra started with a simple problem faced by farmers: limited access to buyers and difficulty comparing available offers.
Our goal was to turn that problem into a practical digital marketplace.
My role was to help turn the idea into a working technical system — from architecture and backend APIs to AWS integration and final deployment.
This experience strengthened my understanding of full-stack development, serverless architecture, AWS, and technical leadership.
And most importantly, it showed me what happens when a team moves from simply discussing an idea to actually building it.
— Vaibhav Shedole Team Captain | Full-Stack & AWS Lead FarmMitra | Bharat Builds
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article