Artem Lyashanov
Interview

Artem Lyashanov: Choosing a database as a strategic decision

Artem Lyashanov, a specialist in transactional business, calls this the main paradox of the industry. In this interview, we will honestly discuss why the architecture of a bygone era is holding back the fintech revolution, how ETL pipelines are losing the battle to data volumes, and what to do when infrastructure turns from a reliable foundation into a major business constraint.

Author Artem Lyashanov
Date 01.10.2026
Section Fintech

The old rules no longer work

For decades, traditional relational databases (RDBMS) were the gold standard in the financial world. Their architecture was built around predictability, local traffic, linear growth, and analytics that could be postponed until the morning.

Fintech traffic has lost its linearity. Viral marketing, market volatility, or a surge in transactions during the holidays create loads that cannot be scaled vertically without loss.

Previously, OLTP (transactions) and OLAP (analytics) existed in different universes. Data was copied from one system to another for hours. For modern fintech, this gap is critical. If there is a delay between an event and a response, the business loses money. Real-time analytics is no longer a bonus, but a survival requirement.

GDPR, PSD2 and new data protection laws in Asia have changed the rules of the game. Security and auditing are no longer cosmetic additions.

Understanding these pain points, it becomes clear why leading fintech companies are migrating en masse to NewSQL and Cloud-Native solutions. How to choose the technology for these challenges is discussed later in our conversation.

Hybrid architecture as an answer to fintech challenges

Interviewer: We outlined the problems: unpredictable traffic, analytics delays and tough regulatory pressure. It seems that traditional databases were simply not designed for such an environment. What solution is considered the most adaptive today?

Artem Lyashanov: In short, this is the concept of Distributed SQL. This is not just another update, but an attempt to get the best of both worlds. For decades, we have chosen between the horizontal scalability of NoSQL and the reliability (ACID guarantees) of traditional relational databases. Distributed SQL removes this compromise.

Interviewer: What exactly is the architectural breakthrough? How is it different from what we have seen before?

Artem Lyashanov: The key idea is to separate the computing layer from the data storage layer. This gives us unprecedented flexibility, in particular, independent scaling, a single source of truth, analytics that see the transaction the second it occurred.

Plaid Case

Interviewer: The theory about Distributed SQL sounds convincing, but let's move on to field conditions. In the world of fintech, the Plaid case has become almost textbook. What engineering challenges did they face at the peak of their growth?

Artem Lyashanov: Plaid is one of the largest providers in the world. Their story is a classic example of a growth crisis for a successful product. At first, they used a standard hosted MySQL stack, but at a certain stage it simply stopped working.

Interviewer: They chose TiDB (cloud-native distributed SQL database). What numbers do we see at the output after the migration?

Artem Lyashanov: The results were very specific. First, operating costs fell by 25%, and this was only due to the rejection of complex sharding. Second, resource utilization increased 5 times thanks to elastic scaling. But the most important thing for engineers is that migrations of huge tables now take place in the background.

Interviewer: So this is a story about savings and stability?

Artem Lyashanov: Not only. The strategic aspect is much more important to me. Plaid has regained its engineering time. Now this time is spent on product development.

Interview guest: Artem Lyashanov

Fintech entrepreneur, expert in payment technologies and transactional business

Artem Lyashanov is a manager with over a decade of experience in the banking and technology sectors.

His career path is a rare combination of technical expertise (CTO), operational management (CEO) and deep legal training. It is this multidisciplinary approach that allows him to see fintech products not as a set of functions, but as holistic systems where technology, regulations and business logic work inextricably linked.

The strategic aspect is much more important to me. Plaid has regained its engineering time. Now this time is spent on product development. — Artem Lyashanov

How we verify information

Every technical claim in our interviews is checked against public standards and vendor documentation, including recommendations from NIST, OWASP, ENISA and ISO/IEC 27001 where they apply to the topic.

We separate verified facts from expert opinion, mark interpretations clearly, and update materials when new regulatory or technical data becomes available.