Pulse BETTING PARIMATCH TECH


With millions of active users, the platform developed by Parimatch Tech is one of the fastest-growing in Eastern Europe. Parimatch Tech has three R&D centres


worldwide, where more than 1000+ IT specialists cover the development and infrastructure support of the Parimatch platform.


infrastructure approach


Parimatch Tech: the benefits of a hybrid


Seamlessly serving 200,000 active users simultaneously, the core processes 7,000 financial transactions per second and, at peak loads, this number reaches 20,000 transactions per second with a latency of 25 ms at 95 pt.


To assist in this, Parimatch Tech integrates the services of many technological giants such as AWS, Google, and Cloudflare, but it's the close relationship with Amazon Web Services that has proven instrumental in cultivating an engineering ethos within the company in recent years.


On November 17, Parimatch Tech and Amazon Web Services took part in a panel discussion at SiGMA Europe Summit examining the benefits business can glean from managed cloud solutions. Dmytro Fedyukov, VP of Data, Deputy CTO and Head of B2B at Parimatch Tech, sat down with G3 to discuss the significance of a hybrid infrastructure approach in developing an engineering ethos.


Could you tell us more about the topics that were under the spotlight at SiGMA?


At its core, the session examined how making technical improvements can significantly expand business possibilities. Using our business case with AWS as an example, we detailed how we improved the scope and delivery of our services to partners and operators.


P84 WIRE / PULSE / INSIGHT / REPORTS


Dmytro Fedyukov VP of Data, Deputy CTO and Head of B2B, Parimatch Tech


When we began working with AWS, we quickly saw that with a few adjustments we can not only profit our existing operators in the white market, but propose some services to other operators who work on our platform and conduct effective business.


How long has the partnership with AWS been in place and what initially drove the decision to move to AWS cloud?


We have been working with AWS for four or five years now. When we initially started working together, Parimatch Tech was at an interesting stage in its journey. We were transitioning from supporting just one operator on our platform in the regulated market of Ukraine to launching operations and initiatives in multiple markets.


Around that time we were solely working in data centres because when you are working with just one operator the metrics are more or less predictable such as how many new users are coming in over a given period. When you then look to launch lots of operator sites in different markets, things become unpredictable.


We needed some flexibility for our services, data, and computation, so decided to develop our own cloud. To achieve this, we found AWS to be an ideal partner whose services and support points could meet our needs.


Now, cloud engineering is part of our development business.


What was the initial transformation process like moving such a large portfolio of data, infrastructure and applications to AWS cloud? Was the transition seamless?


Our first priority was to rebuild our database within AWS and this was a significant project. We needed to motivate our teams, reengineer our products, and alter the organisational structure of Parimatch Tech. Tese were very significant changes designed to optimise our infrastructure and engineering practice. Once these improvements were made, the transformation process became seamless as we moved step by step through different domains and services.


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98