From Startup to Acquisition: Lessons from Building eCommerce

In February 2014, at twenty-two years old and halfway through a technology master's program, the developer set out to build an online marketplace tailored for local vendors who lacked affordable digital storefronts and were often burdened by heavy commissions from major platforms.

Operating with a clear division of labor where the co-founder managed business operations and the developer handled technical infrastructure, the project was completely bootstrapped without any angel funding or incubators. Every hour spent coding was carved out from coursework schedules.

The backend was constructed using Java and Spring, paired with MySQL for persistence and jQuery for the frontend. While not the trendiest stack at the time, it provided the reliability needed for a solo on-call engineer. The MVP was completed in ten weeks of late-night and weekend coding, running on a single Tomcat server that cost twelve dollars a month.

Stock photo for illustration only, not from the actual event

The first major technical hurdle involved integrating two regional payment gateways, each with distinct callback structures and success definitions. An adapter layer was written to normalize these responses into unified internal events such as PAYMENT_CAPTURED and PAYMENT_FAILED, creating the most reusable codebase in the entire architecture.

As the platform crossed the milestone of forty vendors, the initial monolith began showing signs of strain with page load times exceeding three seconds. The inventory service was extracted into a separate process to alleviate the primary bottleneck, all while balancing lectures from morning to afternoon and thesis research during remaining gaps.