INTRODUCTION
Making suppliers and buyers more interconnected
Orbweaver focuses on bringing digital transformation solutions to the electronic components industry. Founded in 2012 in Bethlehem, Pennsylvania, the Orbweaver platform provides an end-to-end quoting, sales automation, and data integration solution for the electronic components industry to create a web of interconnectedness for industry participants, distributors, and OEMs of all sizes. The company helps streamline everything from quoting and sales order intake to customer and supplier integration, helping companies win in a competitive and concentrated market.
THE CHALLENGE
Facing scalability headwinds
In an industry that historically relied on sending email attachments back and forth, Orbweaver wanted to offer a truly digital-native solution. Their Parts Search API helps the process of procuring parts from a bill of materials. This process which includes finding those components, and ensuring they are correct against hundreds of others can be a manual and time consuming endeavor. In the electronics industry, part catalogs easily span into the millions with each part having up to 40 different attributes, creating a deluge of product data. Search plays an absolutely critical role in this process, serving as the starting point for manufacturers and buyers to quickly find what they need. Orbweaver’s DataHub platform specializes in the unique challenges brought upon by such quantities of data and building automation solutions to bring new levels of scale and efficiency.
The Orbweaver team responsible for this digital platform includes Wilmer Companioni, Director of Business Development, Jake Reeves, VP of Technical Operations, and Dave Antosh, the company’s Chief Architect. The team originally used several MySQL databases, but eventually switched to the combination of Amazon DocumentDB for their data and Elasticsearch for core search needs.
Dave Antosh recalls that the journey with Elasticsearch got “difficult and expensive” very quickly. There were noticeable problems specifically around imports, which continually caused a spike in errors. Antosh remembers, “It just started to feel like you really needed a whole team focused on a tool like Elasticsearch for it to work.” Jake Reeves experienced the same limitations, noting “We kept scaling Elasticsearch to try to compensate for the performance, but that was extremely expensive.”
With these concerns in mind, the team knew it was time to make a switch.

