HIMSS: Centralized Data Solution for 20+ Websites

Nowadays, it's a common practice for companies with multiple websites to consolidate their data by gathering and analyzing it using a single centralized source. The Healthcare Information and Management Systems Society (HIMSS), a company managing over 20 conference websites, adopted this approach to streamline the diverse user behavior data they had across their various sites. They required a centralized storage solution to centralize and facilitate the transfer of this data to their analytics service. The primary objective was to create a single solution where the company could store data from all its websites in one easily accessible location.
Project Overview:

• Location: USA
• Product: Website
• Scope of our work: Back-end, Front-end
• Technologies: Drupal, AWS, SASS / SCSS, Bootstrap 4
• Team: Back-end Developers, Front-end Developers, Project Manager
• Timeline: 1 month

We planned to create a dedicated website for centralized storage, based on Drupal, which would utilize its API to aggregate data from various HIMSS websites. Essentially, we developed a microservice to collect and store data from all HIMSS websites. However, after the first phase of development and releasing the solution, an issue arose not due to our solution but with the service used for data analysis. Our primary task was to establish a centralized data storage system that would subsequently transfer data to the analytics service. In 2018, a record-breaking 45,000 users attended the conference within just seven days. When we initiated the data transfer to the analytics service, it encountered a breakdown because it couldn't handle the substantial load from the storage side. This service was vital for HIMSS as it offered advisory features based on user behavior, making it a critical component. Recognizing that the existing server wouldn't meet expectations, we updated the centralized storage system in the second phase of development to:

• Extend the data retention period, anticipating potential future needs beyond the conference.
• Function as a replacement for the previous analytics service, enabling HIMSS to continue operating smoothly during the conference as originally planned.

In the end, we not only successfully created a centralized data storage solution for the company, allowing them to centralize data from various sources, but we also replaced the underperforming analytics services. Remarkably, we managed to develop this replacement feature in a short period of time, ensuring a seamless user experience on the main conference website. This swift action enabled us to maintain the intended behavior and revenue metrics on the website, as originally planned.