Case Study: Librio
Initial Context
When Librio approached us, their monolithic e-commerce platform for selling, managing, and generating personalized books was in a critical state. Located on a single server in Google Cloud, its infrastructure was not only slow but also prone to crashes during traffic spikes, especially noticeable during advertising campaigns. This scenario directly affected the user experience and business stability.
The Challenge
Development Proposal
The Solution
Librio’s infrastructure restructuring began with moving the database to CloudSQL, configuring a highly available instance to meet service demands. Additionally, we integrated Redis into Memorystore to efficiently manage shared cache data. To maximize scalability and better handle the load, we migrated the server to containers within a Kubernetes cluster, allowing for dynamic scaling as needed.
A key change was segregating the book preview generation process, which caused the most system load, moving it to microservices in Cloud Functions and using Cloud Endpoints to handle these operations as a separate API. Moreover, we separated book generation tasks and other critical processes from business logic, running them in isolated containers within “worker” instances, managed through queues and cron jobs to optimize performance and efficiency.
Technologies We Used
In our effort to optimize and transform Librio’s e-commerce platform, we used a variety of tools and platforms. The main ones included:
Google cloud functions
Serverless runtime environment for building and connecting cloud services.