Pretius. Built Smarter: Strategic merger as an answer to modern challenges
Pretius. Built Smarter:
Strategic merger as an answer to modern challenges

How Pretius built a high-performance eCommerce ecosystem for a leading streaming platform

decorative image

Company

Country

–

Industry

Media & entertainment / OTT-VOD streaming

System

eCommerce ecosystem / Subscription & billing

Executive summary: A custom sales ecosystem built to survive flash-crowd traffic

01

Client

A leading OTT/VOD streaming operator in Central Europe, part of a major international media group, running one of its market's top streaming platforms. The platform sells subscriptions and VOD packages to a mass audience, and its commercial success depends on being able to convert huge, sudden surges of interest into completed transactions the moment a hit show premieres.

02

The core challenge

The operator needed a modern, extremely high-performance system to handle mass sales of subscriptions and VOD packages. Its existing solutions couldn't cope with the "flash crowds" that hit at the premieres of the most popular programmes. The decisive challenge was integrating the purchase process with the VOD entitlements system while keeping transactions stable under millions of concurrent sessions, and doing so without losing revenue to failed checkouts at the exact moments demand peaked.

03

Solution delivered

Pretius designed and delivered a complete ecosystem of three integrated systems: an eCommerce platform, a central Product Catalog, and a dedicated Billing system. The architecture was built on a microservices model and optimized for high horizontal scalability on AWS. At its heart was a high-throughput sales engine integrated with multiple payment gateways and a checkout path optimized for mobile devices and Smart TVs. The platform was engineered to handle over 60 million page views per month and remain stable during the market's largest media events.
Key outcomes:
  • Stable sales through peak traffic:
    The platform handles sales reliably during the biggest media events in its market, absorbing flash-crowd spikes that broke the previous setup.
  • Engineered for 60M+ monthly page views:
    The ecosystem was prepared to serve over 60 million page views a month and operate stably under millions of concurrent sessions.
  • Full control over offers and billing:
    The operator gained complete ownership of its offering and settlements, which translated into a significant increase in digital-channel revenue.
  • No more availability gaps at peak load:
    The new system eliminated the service-availability problems that used to strike at moments of highest demand.

Client background

The client is one of the best-known media companies in its market, part of a major international media group, and the operator of a leading OTT/VOD platform. The platform streams a broad catalog of series, films, and live TV to a mass audience, monetized through subscriptions and VOD packages.

In this business, revenue is inseparable from programming moments. When a flagship show premieres, interest doesn't rise gradually. It spikes, often within minutes, as a huge wave of viewers tries to subscribe or buy access at once. In the media industry this pattern has a name: the flash crowd, a near-instantaneous convergence of demand triggered by a single event. For a linear broadcaster, a flash crowd is simply high ratings. For a transactional streaming platform, it is something far more demanding, because every one of those viewers is trying to complete a purchase, receive an entitlement, and start watching in the same narrow window, and each one represents revenue that either lands or is lost in real time.

That dynamic makes the commerce layer mission-critical. It has to convert an enormous, momentary surge of demand into completed, correctly entitled purchases, in real time, on every device from a phone to a Smart TV. The platform's ability to capture revenue is only as good as its ability to stay up and transact when everyone arrives at the same second, which is precisely the moment when infrastructure is most likely to fail and when the business can least afford it.
decorative image

The business challenge: Converting flash crowds instead of collapsing under them

Before the project, the operator's sales processes couldn't withstand sudden, massive surges of user interest, and the business was paying for it directly.
The failure mode wasn't abstract. When a premiere drove a spike the old system couldn't absorb, the consequences landed on both sides of the transaction at once: the business lost revenue it had actively generated demand for, and the users it had just attracted were met with errors instead of the content they'd tried to buy. In a subscription market where a viewer's decision to pay is often tied to a specific show at a specific moment, a checkout that fails during the premiere isn't a deferred sale. It's usually a lost one, and a damaged first impression on top of it.

The situation created several concrete pressures:

  • Flash-crowd traffic at premieres:
    The most popular programme premieres generated enormous, near-instant traffic spikes that existing solutions simply couldn't absorb. These weren't steady growth curves the system could scale into gradually; they were vertical walls of demand arriving in minutes.
  • Lost revenue from failed checkouts:
    When the system faltered, potential revenue was lost to abandoned carts caused by errors, precisely when demand, and therefore the cost of failure, was highest.
  • Broken real-time access:
    Users who did pay couldn't always get real-time access to the content they'd purchased, turning a completed sale into a support complaint and a poor experience at the worst possible moment.
  • Tight coupling to VOD entitlements:
    The purchase process had to integrate cleanly with the VOD entitlements (DRM) system, so that a completed sale immediately and correctly unlocked the right content. That is no small feat when thousands of those sales are settling per minute.

Build vs. buy: why a custom ecosystem, not an off-the-shelf platform

The obvious, low-risk-looking choice would have been to deploy a ready-made eCommerce platform such as Magento. On paper, a boxed solution promises faster time-to-value and less to build. The operator and Pretius deliberately chose the harder path of a dedicated, custom ecosystem, because the obvious option didn't actually solve the problem that mattered.
Two constraints ruled out the off-the-shelf route. The first was performance under the platform's specific integrations: standard eCommerce products aren't designed to sit in the hot path of a VOD entitlements (DRM) system and settle a flood of purchases into real-time content access at flash-crowd scale. The very integration that made the system valuable was the one a boxed platform handled worst. The second was device-level optimization: the platform had to sell smoothly on Smart TVs, a class of device with constrained hardware and idiosyncratic browsers that a generic checkout, tuned for desktop and modern mobile, simply wasn't built for. A custom ecosystem wasn't an engineering indulgence; it was the only option that met the platform's actual performance and integration requirements. This is the recurring lesson of high-scale commerce: the "obvious" build-vs-buy answer inverts once the non-negotiable requirement is throughput and deep integration rather than a catalog and a cart.

The solution: Three integrated systems on a scalable microservices architecture

decorative image
Pretius designed and implemented a complete ecosystem composed of three integrated systems, an eCommerce platform, a central Product Catalog, and a dedicated Billing system, built on a microservices model and optimized for high horizontal scalability on AWS. Decomposing the platform into independent services was itself a deliberate answer to the flash-crowd problem: it let the components most exposed to traffic spikes scale horizontally and independently, rather than forcing the whole system to scale (and fail) as a single block. The central deliverable was a high-throughput sales engine integrated with multiple payment gateways, paired with a checkout path optimized for mobile devices and Smart TVs.

The engagement ran through a disciplined sequence of phases, from analysis and architecture design through development, performance testing, go-live, and ongoing maintenance, following a Waterfall approach in the initial build. That structure suited a project where the architecture had to be proven against load before launch, not iterated into shape afterwards: performance testing was a named milestone in its own right, not an afterthought. A stable seven-developer Pretius team delivered the core implementation, an effort estimated at roughly 700 person-days in the initial phase (about five months of work for the seven-person team). Since go-live, the collaboration has shifted to an Agile model of continuous development and maintenance, a mode it has stayed in ever since.

It's worth being explicit about scope, because the ecosystem's job was tightly defined. Video production and the transmission infrastructure (the CDN) were deliberately left out of scope. Pretius built the commerce and entitlement brain of the platform, the layer that turns demand into paid, authorized access, and integrated it with the streaming infrastructure that delivers the content itself.

The delivery was built around three connected pillars:

01

A high-throughput eCommerce sales engine

The commerce core: a sales engine and checkout process able to convert massive, sudden demand into completed transactions, integrated with multiple payment gateways and optimized end-to-end for mobile and Smart TV. This is the component that had to hold together when a premiere hit, so it received the most aggressive performance engineering.

02

A central Product Catalog

A single, central catalog of offers and packages that gives the operator one source of truth for what's on sale. Centralizing the catalog is what makes fast offer launches possible, because new packages and bundles can be defined once and surfaced consistently across the platform, shortening the time-to-market for new commercial ideas.

03

A dedicated Billing system

A settlements module integrated with the operator's finance function, giving the business full control over billing and reconciliation for its digital sales channel. Owning billing end-to-end, rather than renting it from a third party, is what turned the platform into a controllable revenue channel rather than a black box.

Technologies and key architectural decisions

Every significant architectural decision on this project traced back to the same root requirement: stay correct and fast while the world tries to buy everything at once. Three choices in particular illustrate the depth of that engineering.

A clustered database for transactional integrity under load

The backend runs on Java with MyBatis over a MySQL Percona XtraDB Cluster. The choice of a clustered database was driven by a hard requirement: guarantee high availability and consistency of transactional data even under heavy load, because a commerce platform cannot tolerate lost or inconsistent transactions during exactly the moments it's busiest. The non-trivial part was engineering synchronous replication across the cluster while keeping write latency low. That is the classic tension between consistency and speed, resolved here in favor of never sacrificing transactional integrity, without paying for it in sluggish checkouts.
logo-varnish-cache

Varnish acceleration with entitlement-aware cache invalidation

To handle the sheer volume of requests for the product catalog and subscription statuses, the team put Varnish in front of the API and web layers. Caching is the natural answer to read-heavy traffic, but here it collided with a genuinely hard problem: user entitlements change frequently, and a cache that serves stale entitlement data is worse than no cache at all, because it can show the wrong access state to a paying user. The difficult, non-trivial work was the cache-invalidation logic, keeping cached responses fast and correct despite constant changes in what each user is entitled to see. Getting invalidation right is what let the platform lean heavily on caching for performance without ever compromising the accuracy of who-can-watch-what.
Angular logo

A lightweight frontend engineered for Smart TVs

The frontend is built in Angular, with deliberate optimization for Smart TVs. This is a constraint that's easy to underestimate: TVs ship with limited hardware and unusual, often outdated browser engines, and a frontend that runs beautifully on a modern phone can crawl on a three-year-old television. The team built a lightweight frontend specifically to stay smooth on those older, constrained devices, protecting conversion on a device class that represents a meaningful share of streaming purchases and is easy to neglect.

Cloud, monitoring, and observability

The ecosystem runs on AWS for horizontal scalability, with a full observability stack behind it: the ELK stack (Elasticsearch, Logstash, Kibana) for logging and search, alongside Grafana and InfluxDB for metrics and dashboards. At this scale, observability isn't a nicety. Being able to see, in real time, how the system behaves as a flash crowd builds is what makes it possible to operate confidently through the peaks.

The team

A stable team of seven Pretius developers delivered the core implementation. The initial phase was estimated at around 700 person-days over roughly five months, a concentrated, senior effort rather than a large, diffuse one, which is part of why the architecture stayed coherent enough to still be running and evolving years later.

Engineering for the worst case: security and payment resilience

A public, high-traffic sales platform is a standing target, and the project treated resilience as a first-class requirement rather than a hardening pass at the end. The team went in with an explicit risk assessment, and, tellingly, most of what could go wrong was anticipated and designed for in advance, with only the payment-gateway failures arriving as a genuine surprise.
decorative image

01

DDoS attacks: anticipated, and it happened

Distributed denial-of-service attacks were rated a high-likelihood risk before the project started, and the prediction proved correct: the platform saw numerous attempts to take its servers down. Because the risk was expected, the response was ready, with advanced security and traffic-filtering measures that kept the platform available through the attempts rather than scrambling to react to them.

02

Subscription fraud: anticipated, medium likelihood

The team also anticipated attempts to defraud subscriptions by manipulating the payment process, rated a medium-likelihood risk. These attempts did materialize, and were met with multi-stage transaction verification, adding checks in the purchase flow designed to catch manipulation before it completed, protecting both revenue and the integrity of the entitlements the sales feed.

03

Payment-gateway instability: the unforeseen risk

The one risk the team hadn't priced in was the reliability of the external payment providers themselves. When third-party gateways suffered outages, the platform's own stability was suddenly hostage to someone else's infrastructure. The answer was an automatic failover mechanism that switches to an alternative gateway when one goes down, so an external provider's outage degrades gracefully into a reroute rather than a stopped sale. It's a good illustration of resilient design: the system assumes its dependencies will fail and keeps selling anyway.

Measured outcomes and business impact

A sales ecosystem that turned the platform's busiest, riskiest moments into its most valuable ones.

icon-metric

Engineered for 60M+ page views a month

The platform was prepared to handle over 60 million page views monthly and to operate stably under millions of concurrent sessions, the scale of the market's biggest streaming moments.
Decorative image

Stability at the market's biggest media events

The ecosystem handles sales reliably during the largest media events in the country, absorbing the flash-crowd spikes that previously caused failures. The single most important outcome is the one that's now invisible: the checkout simply works when it matters most.
Decorative image

Significant growth in digital-channel revenue

By taking full control of its offering and settlements, the operator converted a fragile cost center into a dependable, high-performing revenue channel, which translated into a significant increase in revenue from the digital channel. As with any commerce platform, ultimate sales still depend on the appeal of the underlying programming; what the system guarantees is that demand, once created, is reliably captured.
Decorative image

Real-time offer launches

Because the ecosystem is integrated with the entire streaming infrastructure and built around a central catalog, the operator can launch new business models, such as bundles combined with other services, almost instantly, turning commercial ideas into live offers without re-engineering the platform each time.
Decorative image

A key revenue channel, fully owned

After the project, the operator owns a fully custom, scalable sales ecosystem that sits at the center of its digital business, integrated with the whole streaming stack and flexible enough to support new models as the market evolves.
Decorative image

A long-running partnership

Pretius has maintained and developed the system continuously for years, and the relationship has expanded into further areas such as cloud migration and integrations with new platforms. That durability is itself a strong signal about the quality and maintainability of the original build.

Conclusion

This project shows how a purpose-built, cloud-native ecosystem can turn a platform's most dangerous traffic peaks into its biggest revenue moments.

The operator didn't need a generic online store. It needed a commerce ecosystem that could survive flash crowds, unlock purchased content in real time, and run smoothly on everything from phones to older Smart TVs. The "obvious" answer, a boxed platform, would have failed at exactly the requirements that mattered most: throughput at peak, deep integration with VOD entitlements, and device-level optimization for Smart TV. By choosing the harder path, three integrated systems on a scalable AWS microservices architecture, engineered for transactional integrity, entitlement-aware caching, and constrained devices, then hardened against DDoS attacks, fraud, and even payment-gateway outages, Pretius built a platform prepared for over 60 million page views a month and stable at the scale of the market's biggest premieres.

The result has been a key revenue channel for the operator, and a partnership Pretius has continued to grow over many years. For any transactional platform whose busiest moment and its most fragile moment are the same moment, that's the whole game: infrastructure that is most dependable precisely when everything depends on it.

Looking for a software development company?

Work with a team that already helped dozens of market leaders. Book a discovery call to see:

  • How our products work
  • How you can save time & costs
  • How we’re different from other solutions

footer-contact-steps

We keep your data safe: ISO certified

We operate in accordance with the ISO 27001 standard, ensuring the highest level of security for your data.
certified dekra 27001
© 2026 Pretius. All rights reserved.