FortiGate, pfSense and MikroTik: How Firewalls Work and Which One to Choose
28. 04. 2021
9 min read
Datasheet: Database Optimisation
Except for common relational databases such as MySQL and its follower MariDB, we can cope with object-relational database PostgreSQL. We are familiar with the NoSQL database concept as well.
The optimisation is only done after a thorough monitoring and data analysis of an existing solution has been finished. Hence based on our experience from datacentre and software development, the optimisation is proposed to fit your needs.
We will help you to implement and configure the Galera cluster, which guarantees high SQL Database availability. We can also help with a schemaless databaseElasticsearch, which is suitable for unstructered data.
Phone number database is still a crucial part of our applications which removes unsolicited phone calls Numbo Call Blocker. In order to face up to an issue of high latency and to increase database capacity, we did a thorough optimisation. In the chart you can see how the database features changed.
|Before optimisation||During optimisation|
|Items in the database||app. 80 thousand||app. 14 million|
|Latency||30–90 s||less than 1 s|
|Number of clients performing data updates||2–5||unlimited|
|Server infrastructure||One server in CR||Multiple servers around the world – always close to the client|