INTRODUCTION
Founded in Melbourne in 2005, New Aim started as an eBay seller. Over the years, it grew into one of Australia’s largest private ecommerce technology companies, selling products through more than 35 major retailers including Myer, Big W, and Woolworths.
In 2012, New Aim built and launched its proprietary marketplace, Dropshipzone, which is used by more than 2,500 small and medium retailers across Australia and New Zealand. Dropshipzone removes the complexities of managing inventory and supply chain operations by connecting suppliers, retailers, and end customers in a seamless ecosystem. Dropshipzone also helps retailers to quickly scale and grow.
“As a technology company, data is core to everything we do,” said John Barkle, General Manager of Dropshipzone. “We have a team of 40 experts focused on building, maintaining, and innovating around the platform.”
Working with MongoDB—first through the MongoDB Community Edition, and later in 2024 through a migration to MongoDB Atlas—has been instrumental to New Aim’s growth.
“Moving to MongoDB Atlas gave us access to a fully managed, flexible database. It helped us manage data more efficiently, and remove complexity,” said Barkle.
THE CHALLENGE
Unlocking scale and flexibility
New Aim built Dropshipzone on the Community Edition of MongoDB, which came with the eCommerce solution Magento (now Adobe Commerce). Building Dropshipzone on MonogDB Community Edition allowed the team to take advantage of MongoDB's document model, and quickly build an incredibly innovative platform.
In the next decade, however, Dropshipzone experienced constant growth, which came with significant challenges:
- Scaling requirements: New Aim offers products across more than 40 channels, including online stores, marketplaces, and omnichannel retailers. Over 200 suppliers are contributing to the New AIm marketplace today, and the number of SKUs it lists is over 100,000.
- A complex data architecture: New Aim’s platform needed to manage a vast and complex ecosystem of retailers, suppliers, and products, as well as diverse datasets—including supplier catalogs, retailer preferences, and datasets related to pricing and promotion.
- Performance bottlenecks: High page load times were negatively affecting user experience and engagement.
- Operational inefficiencies: Without a cloud-based solution, monitoring and scaling databases became cumbersome. This led to frequent downtime, including two major incidents of over one hour in FY23, and reduced development velocity as over 50% of developers’ time was spent on ‘business as usual’ tasks and incident support.

