INTRODUCTION
Connecting skilled workers to local jobs in 74+ Indian cities
Apna's talent-matching algorithm has enabled successful pairing of suitable candidates with relevant job openings, ultimately bridging the gap between employers and job seekers. As a result, the platform is playing a vital role in promoting employment and fostering economic growth in India.
“India is still developing its economy, and unemployment is rife,” says Suresh Khemka, Head of Platform Engineering at Apna. “People want to work. There are opportunities out there, but they’re hard to find. We provide a central platform for job seekers to find jobs, advertise their services, and connect with their local communities.”
Founded in 2019, Apna is already India’s leading jobs and professional networking platform. It operates across 74 cities and is used by big-name companies, such as Burger King, Zomato, and Delhivery, and by tradespeople, like delivery drivers, service workers, and more. The company also partners with leading public sector institutions, such as UNICEF, YuWaah, and the Ministry of Minority Affairs of India, to support the National Skill Development Corporation.
THE CHALLENGE
Breaking away from the shackles of monolithic architecture
Apna users can access unlimited job listings by creating an account with just their phone number. But with 30 million users and 400,000 employers posting up to 700 times a month, the company needs to do more than simply display information.
Data needs to be relevant, personalized, and highly available to help match the right person to the right job. Apna also needs to verify employers posting on the platform to protect workers from fraud.
“As a start-up, we wanted to get moving quickly, but when the business began to grow we realized our monolithic infrastructure was slowing us down and lacked scalability,” recalls Khemka. “We need to be able to hone our app and roll out new features quickly.”
Apna switched from monolithic to microservices in September 2021 but needed more flexibility than its PostgreSQL relational database, which was integrated with Elasticsearch, offered. Not only difficult to scale, it was also becoming costly and complex to maintain, which led to outages and performance issues.
“We had 100 microservices running and two viable options: find a great database and learn how to run it in house; or use a cloud-based solution,” Khemka explains. “We decided to look for a cloud solution so we could focus on developing our platform.”
