Technology
eMAG Marketplace Infocenter Ecosystem: keeping a multilingual marketplace fast and stable
eMAG Marketplace Infocenter Ecosystem: keeping a multilingual marketplace fast and stable

Eduard Abrudan
Eduard Abrudan
Eduard Abrudan
Multilingual Platform · Google Cloud · Faster Delivery
Multilingual Platform · Google Cloud · Faster Delivery


eMAG Marketplace Infocenter became a faster and more stable multilingual platform, cutting average page load time from 4.2 seconds to under 2 seconds and strengthening deployment, observability, and infrastructure control across Google Cloud Platform.
The eMAG Marketplace Infocenter project sits inside a multilingual enterprise ecosystem that serves a large regional marketplace. In that kind of environment, performance and stability are connected: traffic, caching, deployments, observability, and security all affect each other, so the system has to stay predictable while it keeps moving.
Our work focused on one clear outcome: make the platform faster and easier to operate without disrupting delivery. The system already had business logic, scale, and regional complexity, so the job was to improve the parts that shape daily performance and give the team better control over the infrastructure behind it.
What needed fixing
The platform had grown into a complex WordPress application with a lot of custom PHP business logic, legacy code, and older dependencies. That made maintenance heavier, slowed down development, and raised the effort needed to deliver new functionality consistently.
The infrastructure needed the same level of attention. Environment separation had to be introduced, deployment reliability had to improve, and the whole setup needed to become easier to operate across development, staging, and production.
How we approached it
Elisium Tech took over the technical delivery and led the modernization effort across both the application and infrastructure layers. The work included migration from Microsoft Azure to Google Cloud Platform, creation of dedicated Development, Staging, and Production environments, application performance optimization, and delivery of the new Service Providers module.
The infrastructure was built around Google Cloud Platform services such as Cloud Run, Cloud SQL, Cloud Armor, and Artifact Registry, with GitLab CI/CD handling deployment automation. A stronger caching strategy was introduced for the customized WordPress application, while observability and logging workflows were improved so the team could detect issues earlier and react before they reached end users.
Main challenges
The hardest part was working inside a multilingual ecosystem with complex caching behavior and several deployment environments. Speed, consistency, and maintainability had to stay aligned, even while the platform was handling real traffic and a large amount of business logic.
Visibility was the other major challenge. The platform needed clearer insight across distributed services without weakening delivery reliability or security, so performance work, cloud-native infrastructure, observability, and WAF protection had to be handled as one strategy rather than separate tasks.
What changed
The result was a faster platform with more stable deployment workflows and better visibility across the infrastructure ecosystem. After the caching and infrastructure optimization work, average page load time dropped from 4.2 seconds to under 2 seconds.
Deployment reliability improved, operational complexity decreased, and the team gained a clearer foundation for future development. The new Service Providers functionality also added practical business value by supporting day-to-day operations inside the platform.
Business impact
The modernization effort turned a complex legacy WordPress setup into a faster and more maintainable production system. It also introduced a stronger cloud infrastructure on Google Cloud Platform, complete with separated environments and a cleaner deployment model.
In practice, that meant fewer infrastructure bottlenecks, better resilience across environments, and a platform that could continue evolving without losing control of the operational side. Following the delivery, the project continued under the client’s primary organization, which confirmed the quality and maintainability of the implemented solution.
Technical highlights
WordPress.
Custom PHP.
Google Cloud Platform.
Cloud Run.
Cloud SQL.
Cloud Armor.
Docker.
NGINX.
GitLab CI/CD.
Artifact Registry.
Multi-environment deployment.
Advanced application caching.
Legacy system modernization.
Performance optimization.
Team
The project involved one development specialist, one DevOps & infrastructure architecture specialist, and one project management specialist.
Disclaimer
Project delivered as a subcontractor for Two and From. Elisium Tech was responsible for the technical delivery, architecture, infrastructure modernization, and development of the solution.
eMAG Marketplace Infocenter became a faster and more stable multilingual platform, cutting average page load time from 4.2 seconds to under 2 seconds and strengthening deployment, observability, and infrastructure control across Google Cloud Platform.
The eMAG Marketplace Infocenter project sits inside a multilingual enterprise ecosystem that serves a large regional marketplace. In that kind of environment, performance and stability are connected: traffic, caching, deployments, observability, and security all affect each other, so the system has to stay predictable while it keeps moving.
Our work focused on one clear outcome: make the platform faster and easier to operate without disrupting delivery. The system already had business logic, scale, and regional complexity, so the job was to improve the parts that shape daily performance and give the team better control over the infrastructure behind it.
What needed fixing
The platform had grown into a complex WordPress application with a lot of custom PHP business logic, legacy code, and older dependencies. That made maintenance heavier, slowed down development, and raised the effort needed to deliver new functionality consistently.
The infrastructure needed the same level of attention. Environment separation had to be introduced, deployment reliability had to improve, and the whole setup needed to become easier to operate across development, staging, and production.
How we approached it
Elisium Tech took over the technical delivery and led the modernization effort across both the application and infrastructure layers. The work included migration from Microsoft Azure to Google Cloud Platform, creation of dedicated Development, Staging, and Production environments, application performance optimization, and delivery of the new Service Providers module.
The infrastructure was built around Google Cloud Platform services such as Cloud Run, Cloud SQL, Cloud Armor, and Artifact Registry, with GitLab CI/CD handling deployment automation. A stronger caching strategy was introduced for the customized WordPress application, while observability and logging workflows were improved so the team could detect issues earlier and react before they reached end users.
Main challenges
The hardest part was working inside a multilingual ecosystem with complex caching behavior and several deployment environments. Speed, consistency, and maintainability had to stay aligned, even while the platform was handling real traffic and a large amount of business logic.
Visibility was the other major challenge. The platform needed clearer insight across distributed services without weakening delivery reliability or security, so performance work, cloud-native infrastructure, observability, and WAF protection had to be handled as one strategy rather than separate tasks.
What changed
The result was a faster platform with more stable deployment workflows and better visibility across the infrastructure ecosystem. After the caching and infrastructure optimization work, average page load time dropped from 4.2 seconds to under 2 seconds.
Deployment reliability improved, operational complexity decreased, and the team gained a clearer foundation for future development. The new Service Providers functionality also added practical business value by supporting day-to-day operations inside the platform.
Business impact
The modernization effort turned a complex legacy WordPress setup into a faster and more maintainable production system. It also introduced a stronger cloud infrastructure on Google Cloud Platform, complete with separated environments and a cleaner deployment model.
In practice, that meant fewer infrastructure bottlenecks, better resilience across environments, and a platform that could continue evolving without losing control of the operational side. Following the delivery, the project continued under the client’s primary organization, which confirmed the quality and maintainability of the implemented solution.
Technical highlights
WordPress.
Custom PHP.
Google Cloud Platform.
Cloud Run.
Cloud SQL.
Cloud Armor.
Docker.
NGINX.
GitLab CI/CD.
Artifact Registry.
Multi-environment deployment.
Advanced application caching.
Legacy system modernization.
Performance optimization.
Team
The project involved one development specialist, one DevOps & infrastructure architecture specialist, and one project management specialist.
Disclaimer
Project delivered as a subcontractor for Two and From. Elisium Tech was responsible for the technical delivery, architecture, infrastructure modernization, and development of the solution.
About The Author


Eduard Abrudan
Head of Technology and Partner at Zendra Group
Eduard Abrudan is Head of Technology and Partner at Zendra Group, with over 12 years of experience in software development, cloud architecture, and DevOps. He leads the technical direction of projects, supports teams in solving complex challenges, and turns business requirements into scalable software solutions. He is also the founder of Elisium Tech, specializing in AWS architecture, data platforms, and the integration of artificial intelligence into digital products.

