Remove Architecture Remove Database Remove Processing Remove Tuning
article thumbnail

Fine-Tuning Performance, Resolving Common Issues in FinTech Application With MySQL

DZone

Relational Databases are the bedrock of any FinTech application, especially for OLTP (Online transaction Processing). This foundational component in any application architecture usually poses challenges around scaling as the business expands rapidly.

FinTech 258
article thumbnail

What is cloud-native architecture? Set yourself up for cloud success

Dynatrace

To take full advantage of the scalability, flexibility, and resilience of cloud platforms, organizations need to build or rearchitect applications around a cloud-native architecture. So, what is cloud-native architecture, exactly? What is cloud-native architecture? The principles of cloud-native architecture.

Cloud 162
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Comparing PostgreSQL DigitalOcean Performance & Pricing – ScaleGrid vs. DigitalOcean Managed Databases

Scalegrid

ScaleGrid is a fully managed DBaaS that supports MySQL, PostgreSQL and Redis™, along with additional support for MongoDB® database and Greenplum® database. Along with many popular cloud providers, DigitalOcean also provides a Managed Databases service. So, which database service is right for your application? Single Node.

Database 230
article thumbnail

How To Scale a Single-Host PostgreSQL Database With Citus

Percona

Rather than listing the concepts, function calls, etc, available in Citus, which frankly is a bit boring, I’m going to explore scaling out a database system starting with a single host. I won’t cover all the features but show just enough that you’ll want to see more of what you can learn to accomplish for yourself.

Database 102
article thumbnail

10 tips for migrating from monolith to microservices

Dynatrace

Transforming an application from monolith to microservices-based architecture can be daunting, and knowing where to start can be difficult. Because monolithic applications combine database, client-side interfaces, and server-side application elements in a single executable, they’re difficult to understand, even for their own administrators.

article thumbnail

PostgreSQL Connection Pooling: Part 1 – Pros & Cons

Scalegrid

In that environment, the first PostgreSQL developers decided forking a process for each connection to the database is the safest choice. It would be a shame if your database crashed, after all. On modern Linux systems, the difference in overhead between forking a process and creating a thread is much lesser than it used to be.

article thumbnail

PostgreSQL Connection Pooling: Part 3 – Pgpool-II

Scalegrid

Check out the Pgpool-II architecture that supports all of its features, and learn how the connection pooler works. Pgpool-II has a more involved architecture than PgBouncer in order to support all the features it does. The Pgpool-II parent process forks 32 child processes by default – these are available for connection.

Cache 264