Remove Architecture Remove Database Remove Scalability Remove White Paper
article thumbnail

What Adrian Did Next?—?Part 2?—?Sun Microsystems

Adrian Cockcroft

I became the Sun UK local specialist in performance and hardware, and as Sun transitioned from a desktop workstation company to sell high end multiprocessor servers I was helping customers find and fix scalability problems. We had specializations in hardware, operating systems, databases, graphics, etc.

Tuning 52
article thumbnail

Setting Up and Deploying PostgreSQL for High Availability

Percona

Unfortunately, using certain open source database software as part of an HA architecture can present significant challenges. This blog highlights considerations for keeping your own PostgreSQL databases highly available and healthy. The same changes made in the primary database are made in the replicas.

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

ABAC on SpiceDB: Enabling Netflix’s Complex Identity Types

The Netflix TechBlog

A cleanup process to prune stale relationships from the database. The Beginning of SpiceDB Caveats The SpiceDB community had already explored integrating SpiceDB with Open Policy Agent (OPA) and concluded it strayed too far from Zanzibar’s core promise of global horizontal scalability with strong consistency.

Cache 249
article thumbnail

An Introduction to MySQL Replication: Exploring Different Types of MySQL Replication Solutions

Percona

MySQL replication is a process in which data from a primary MySQL database is copied and sent to one or more secondary databases, known as replicas. Setting Up MySQL Replication – Step by Step: Backup Data: Before starting, create a backup of your primary database to prevent data loss during setup.

Servers 52
article thumbnail

Is It a Read Intensive or a Write Intensive Workload?

Percona

One of the common ways to classify database workloads is whether it is “read intensive” or “write intensive”. Because recognizing if the workload is read intensive or write intensive will impact your hardware choices, database configuration as well as what techniques you can apply for performance optimization and scalability.