Kakava.lt

Concurrent buyers. The client’s benchmark: 1 000 people purchasing tickets in the same moment, without the system blinking.

The platform was doing its job, but it was carrying the weight of its own history.

-> Built on .NET 4 – internal libraries that were never designed for high-traffic bursts.

-> A single database, managed through Entity Framework, that felt the strain every time a big event went on sale.

-> Reports baked into the live system, so every time a promoter pulled numbers, the database slowed down for everyone else, including buyers at checkout.

-> A steady stream of regulatory changes like VAT changes that the platform had to absorb without missing a beat.

• Hold up during peak sales – the target is 1,000 people buying at the same moment.
• Keep improving reliability and service day to day.
• Ship the convenience features that promoters and buyers actually ask for.
• Modernise the technology base without disrupting a business

The obvious move was to rebuild the whole thing. We priced it, planned it, and put a full system-rewrite plan on the table. The client looked at the cost and at the risk of pausing a live ticketing business – and chose a different path. So did we. Instead of a big-bang rewrite, we modernise in place, module by module, on a system that keeps selling every day.

• Investigated incidents as they happened and turned each one into a concrete, lasting fix.
• Introduced a queue service to absorb traffic spikes, so a sudden rush of buyers waits in an orderly line instead of overwhelming the system all at once.
• Optimised the database and the code where it mattered most: the paths that carry the heaviest load during a sale.
• Rebuilt the reports system so promoters pull their numbers from outside the transactional path, keeping the database free for buyers while a sale is live.
• Kept the platform current with regulatory changes such as VAT, so compliance never turns into a fire drill.

• Big sales are calmer. The spikes that used to cause stress are absorbed by the queue service, and the database no longer fights the reports for resources when a sale is live.
• Promoters get more. New features and self-serve reporting mean event organisers can do more on the platform without leaning on support.
• The foundation keeps improving. Every module we modernise makes the next one easier: the technology base moves forward without the business ever standing still.
• Performance work continues. The 1,000-concurrent-buyer target is the bar we’re building toward. The platform is measurably steadier, and the gradual modernisation is ongoing – with the client looking forward to the next round of improvements.

A ticketing platform is only as good as its worst day – the moment a headline show sells out in minutes. Kakava.lt has fewer of those bad days now, and every module we modernise makes the next big sale a little quieter.