Scaling out PostgreSQL for CloudFlare Analytics using CitusDB
lundi 8 juin 2015 à 17:54@jeekajoo shaarlinks 08/06/2015
dans la continuité de mon précédent shaarlink, cloudflare explique pourquoi ils ont forké postgresql pour leurs besoins de stockage d'évènements nginx..
"""
CitusDB has also maintained compatibility with PostgreSQL, not by forking the code base like other vendors, but by extending it to plan and execute distributed queries. Furthermore, CitusDB used the concept of many logical shards so that if we were to add new machines to our cluster, we could easily rebalance the shards in the cluster by calling a simple PostgreSQL user-defined function.
With CitusDB, we could replicate logical shards to independent machines in the cluster, and automatically fail over between replicas even during queries. In case of a hardware failure, we could also use the rebalance function to re-replicate shards in the cluster.
"""
(Permalink)
dans la continuité de mon précédent shaarlink, cloudflare explique pourquoi ils ont forké postgresql pour leurs besoins de stockage d'évènements nginx..
"""
CitusDB has also maintained compatibility with PostgreSQL, not by forking the code base like other vendors, but by extending it to plan and execute distributed queries. Furthermore, CitusDB used the concept of many logical shards so that if we were to add new machines to our cluster, we could easily rebalance the shards in the cluster by calling a simple PostgreSQL user-defined function.
With CitusDB, we could replicate logical shards to independent machines in the cluster, and automatically fail over between replicas even during queries. In case of a hardware failure, we could also use the rebalance function to re-replicate shards in the cluster.
"""
(Permalink)