# Cluster Published articles for Cluster. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AWS Elastic Beanstalk introduces Cluster Mode DevFeed: [AWS Elastic Beanstalk introduces Cluster Mode]() Original publisher: [Read original article]() Author: Channy Yun (윤석찬) Published: 2026-09-17T19:20:21Z Content type: release Language: en Sources: [AWS News Blog]() Topics: [Amazon Web Services](), [Deployment](), [Amazon EKS](), [autoscaling](), [Monitoring](), [observability](), [Provisioning](), [Secrets Management](), [AWS Certificate Manager](), [CI/CD]() Tags: [amazon-eks](), [amazon-elastic-kubernetes-service](), [application](), [autoscaling](), [aws](), [aws-certificate-manager](), [aws-elastic-beanstalk](), [ci-cd](), [cluster](), [code](), [compute](), [container](), [deployment](), [dockerfiles](), [https](), [infrastructure](), [kubernetes](), [launch](), [monitoring](), [news](), [provisioning]() ### AI overview AWS Elastic Beanstalk introduces a fully managed Cluster Mode that runs multiple applications on shared infrastructure powered by Amazon EKS. It also highlights AI-assisted environment analysis, GitHub Actions deployment, observability, traffic-splitting deployments with rollback, autoscaling, secrets management, and HTTPS by default. ### Source excerpt Run an application on AWS Elastic Beanstalk Cluster Mode without provisioning or operating the compute underneath it. You provide a container image or source code; Elastic Beanstalk with service-operated compute creates and operates the environment that runs it. ## Kubernetes Multi-Cluster Project Karmada Reaches CNCF Graduation DevFeed: [Kubernetes Multi-Cluster Project Karmada Reaches CNCF Graduation]() Original publisher: [Read original article]() Author: Claudio Masolo Published: 2026-09-17T10:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Kubernetes](), [Orchestration](), [Cloud](), [Computing]() Tags: [ai-architecture](), [cloud](), [cluster](), [clusters](), [cncf](), [devops](), [karmada-kubernetes-cncf](), [kubernetes](), [multi-cloud](), [news](), [orchestration](), [project](), [release]() ### AI overview The CNCF announced that Karmada, a multi-cluster and multi-cloud Kubernetes orchestration project, graduated to its highest maturity tier. The announcement coincided with Karmada v1.19, which improves multi-component scheduling for AI training jobs and makes priority-based scheduling available by default in Beta. ### Source excerpt The Cloud Native Computing Foundation (CNCF) announced on September 2026 that Karmada, a multi-cluster and multi-cloud Kubernetes orchestration project, has graduated. This multi-cluster and multi-cloud Kubernetes orchestration project reached CNCF's highest maturity tier. By Claudio Masolo ## Too many GCache Page Files in MySQL Data Directory DevFeed: [Too many GCache Page Files in MySQL Data Directory]() Original publisher: [Read original article]() Author: Kedar Vaijanapurkar Published: 2026-09-17T05:29:14Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [XtraDB Cluster (PXC)](), [Replication](), [Transactions](), [MySQL]() Tags: [cluster](), [database-administration](), [disk-space](), [galera](), [galera-replication](), [gcache](), [gcache-freeze-purge-at-seqno](), [gcache-keep-pages-count](), [gcache-page](), [gcache-page-files](), [gcache-purge](), [gcache-troubleshooting](), [mysql](), [mysql-disk-space](), [mysql-troubleshooting](), [percona-xtradb-cluster](), [pxc](), [replication](), [xtradb-cluster-pxc]() ### AI overview An investigation into thousands of GCache page files accumulating in a Percona XtraDB Cluster data directory. The article explains how frozen GCache purging caused disk growth, links the behavior to a cluster partition, and describes reproducing it by setting gcache.freeze_purge_at_seqno and generating workload. ### Source excerpt Learn why PXC accumulates thousands of gcache.page.* files, how frozen GCache purging causes disk growth, and how to safely recover and rejoin using IST. The post Too many GCache Page Files in MySQL Data Directory appeared first on Percona. ## Fat Rail vs Thin Rail in AI compute clusters DevFeed: [Fat Rail vs Thin Rail in AI compute clusters]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-01T07:30:18Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Artificial Intelligence](), [Job](), [datasets]() Tags: [400g](), [ai](), [cluster](), [clusters](), [compute](), [data](), [fabric](), [fat-rail](), [internet-architecture](), [switching](), [thin-rail]() ### AI overview The article explains "fat" and "thin" rails in AI compute clusters. The terms describe whether a node's connection to the fabric provides sufficient bandwidth for the workload, with the practical distinction determined by node-to-node traffic rather than cable count alone. ### Source excerpt We are starting to hear about "Thin" and "Fat" rails in AI fabrics. These are just another way to say a connection from compute into the Fabric. The link either has sufficient capacity (Fat) or insufficient capacity (Thin). A thin rail provides the node with a single path into the fabric. That may be one ... Read more The post Fat Rail vs Thin Rail in AI compute clusters appeared first on Justin Wilson (j2sw). ## ansible-k3s-on-vms updated to Debian 13 (Trixie) DevFeed: [ansible-k3s-on-vms updated to Debian 13 (Trixie)]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2025-11-13T04:30:00Z Content type: release Language: en Sources: [stafwag Blog]() Topics: [Ansible](), [k3s](), [Debian](), [Raspberry Pi](), [virtual machines](), [Cloud]() Tags: [ansible](), [changelog](), [cloud](), [cloudinit](), [cluster](), [debian](), [debugging](), [k3s](), [kubernetes](), [linux](), [pi](), [pi-4](), [release](), [virtual-machines]() ### AI overview The article announces updated Ansible roles for provisioning virtual machines and deploying k3s on a Raspberry Pi 4 cluster. The roles were updated for Debian 13 Trixie and include new templates, examples, and fixes across several roles. ### Source excerpt I use the lightweight Kubernetes K3s on a 3-node Raspberry Pi 4 cluster. And created a few ansible roles to provision the virtual machines with cloud image with cloud-init and deploy k3s on it. I updated the roles below to be compatible with the latest Debian release: Debian 13 Trixie. With this release comes a new movie ;-) ## How Klarna Migrated the KRED System from Mnesia to Postgres with Zero Downtime DevFeed: [How Klarna Migrated the KRED System from Mnesia to Postgres with Zero Downtime]() Original publisher: [Read original article]() Author: Onno Vos Dev Published: 2025-02-26T09:04:27Z Content type: article Language: en Sources: [Klarna Engineering]() Topics: [Databases](), [Erlang](), [Replication](), [sharding](), [Transactions](), [systems]() Tags: [cluster](), [databases](), [erlang](), [klarna](), [memory](), [postgresql](), [production](), [replication](), [scaling](), [sharding](), [software-development](), [software-engineering](), [transactions]() ### AI overview This article describes Klarna's migration of KRED, an Erlang servicing system, from Mnesia to Postgres with zero downtime. It explains the original replicated seven-node architecture, the system's scaling challenges, and a plan involving sharding across multiple clusters. ### Source excerpt How we migrated from Mnesia to Postgres with zero downtime Back in December 2004, an Erlang application was born called KRED (referring to the freshly-started company called Kreditor, now known as Klarna). KRED is one of the "servicing systems" at Klarna and keeps track of consumer debt (among other things). It was powered by Mnesia and consisted of a cluster of 7 nodes, each holding a full copy of the database on disk. The data was replicated using a custom replication mechanism built in-house by Klarna. One node was elected as the leader and its database was considered the source of truth in the system. All database transactions were executed on the leader and writes were replicated to the rest of the nodes, the so-called followers. The Mnesia database was around 15 TB and at its peak in 2018 around 1.3 TB was held in memory at all times. Considering that few suppliers were selling hardware with such specs, it's easy to claim the crown of one of the biggest Mnesia databases in terms of in-memory storage, that was running in production. The rest of the data was offloaded to disk using mnesia_eleveldb. KRED has been a stable workhorse at Klarna so why change a winning concept? Get ready, for a two part blog post where we'll first go through our journey of how we went about this and secondly, how we made Mnesia behave just like Postgres and implemented our version serializable isolation level on top of Postgres! How the journey started Three engineers, sat down in a bar in Stockholm, Sweden and asked this question: 'When Klarna truly takes off, will KRED survive? Assuming "no", and presented with a blanco check, how would we tackle this problem?' The answer quickly revolved around the issues of running Mnesia on an even larger cluster and with leveldb compaction hitting some hot tables during peak times. One can only imagine how that problem would just continue to get worse over time. Considering the three engineers had worked on KRED for a long time, scaling KRED wa ## March Update: Making waves DevFeed: [March Update: Making waves]() Original publisher: [Read original article]() Published: 2024-03-17T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [smart speaker](), [Home Assistant](), [Hardware](), [Embedded Software Dev]() Tags: [cluster](), [firmware](), [fosdem](), [hardware](), [headphones](), [home-assistant](), [ironos](), [pinecil](), [pinetime](), [pinevox](), [smart-speaker](), [update]() ### AI overview Pine64's March update describes two products in development: the PineVox, a BL606P-based smart speaker intended for Home Assistant voice interactions, and unnamed bone-conduction headphones using the BES2300 chipset. The PineVox is undergoing firmware development, while the headphones' enclosure and software are not yet final. ### Source excerpt Banner artwork: Caffeine New products in development Authors: Ralim, gamiee As probably one of the most anticipated sections of the blog, we can confirm that there are more new products in the pipeline. The first two were shown at the FOSDEM table in Feburary. PineVox - Virtual assistant The PineVox is a BL606P based home assistant smart speaker. Designed to help build a good community option for voice interactions with software such as Home Assistant. Currently a small number of developer seed units have been given out. Work is ongoing by Ralim & Gamiee to get a minimal firmware image ready to allow for demonstration and to prove all hardware fully functional etc. More information on the unit should be available soon on our new documentation page. Features of note include the hardware microphone kill switch, and the ability to debug the unit externally. The hardware microphone killswitch allows the software to mute the microphone but unmuting has to be performed using the button on the device. Muting the microphone disables the clock connection to the microphone, giving peace of mind that it really, really isnt listening to you. Giving users control of the smart devices in their home and allowing for you to control the security is important, and we are working on the PineVox to help enable that future. Another notable aspect worth mentioning is the speaker. Designed specifically for voice applications rather than music playback, it ensures clear and high-quality voice audio reception. Bone conduction headphones These are a set of bone conduction headphones using the same BES2300 chipset as found in the PineBuds Pro. The plan is to expand OpenPineBuds project with support for these before they enter manufacturing. Currently there is amazing work going on to sort out licencing of the BES2300 codebase; so work to support these is being done carefully to minimise impact on the code base. The enclosure design is not final yet, nor is the software complete. However in th ## Outage January 21st DevFeed: [Outage January 21st]() Original publisher: [Read original article]() Published: 2024-01-21T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Website](), [Wiki](), [version]() Tags: [beta](), [bugs](), [cluster](), [community](), [documentation](), [issue](), [outage](), [pages](), [state]() ### AI overview PINE64 reports an outage affecting its main cluster and says it is investigating the cause. A temporary beta website has been deployed, while documentation pages may be unstructured, outdated, and inconsistent with the wiki's current state. ### Source excerpt We regret to inform you that we are currently experiencing an outage in our main cluster. We are currently actively investigating the cause of this issue. We understand the inconvenience this may cause and appreciate your patience during this time. In the meantime, we have deployed a beta version of our website to ensure that information are still reachable for the community. Please note that this is a quick and temporary solution - bugs are expected and the documentation pages are not structured yet and might be outdated and not reflect the current state of the wiki, which is affected by the outage as well. Thank you for your understanding! ## Cluster build log: Moving to temporary cluster DevFeed: [Cluster build log: Moving to temporary cluster]() Original publisher: [Read original article]() Published: 2021-09-01T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [hosting](), [Network](), [Ethernet]() Tags: [cluster](), [community](), [downtime](), [ethernet](), [hosting](), [network](), [rockpro64-2]() ### AI overview This build log explains why PINE64 is creating a temporary hosting cluster. The existing cluster needs hardware changes that require extended downtime, so a smaller cluster will keep community services running during the work. The article introduces the power and network requirements for the temporary cluster. ### Source excerpt As promised in the last month's community update Housekeeping section, this is the first part of the cluster's build log! This mini-series in which I will cover everything about upcoming changes our hosting cluster, and it begins with building a temporary cluster. Why build a temporary cluster? One of the latest photo of cluster Let's start from beginning. When we built the current hosting cluster a year ago, it was made in quite a hurry (some of the services needed to be migrated to the cluster on a moment's notice). Also, it was the first time I (gamiee) and Matthew (fire219) were tasked with building a cluster. Because of this, some of the cluster's features are missing and various things don't work quite as well as we have hoped. For example, the cluster has power management boards (PCB on right side of every row), which are used primary for power distribution to the SBCs, but also it also has a I2C GPIO Expander for rebooting and turning off the SBCs. The I2C Expansion isn't in use yet, because the primary node wasn't able to detect it, so this is something that needs to be checked out when the cluster is turned off. And this is exactly the main reason why we are building a temporary cluster. We need to do some changes which require us to have the whole cluster turned off and on a workbench (not in housing room where isn't much space), and this means that it will be inaccessible for several days. Obviously a long downtime wouldn't be good when 100% of PINE64 community services are running on it. So we are going to build a temporary small cluster, which will have the minimal number of required nodes to have all services running, so we can make all upgrades with precision and at our own pace. What do we need to make a custom cluster? There are two things each node needs: a power supply and access to the network. Access to the network can be solved by using a classic Ethernet switch, but powering multiple RockPros, which are actually pretty power hungry, is a bit ## June Update: postmarketOS CE PinePhone, Shipping & PINE64 Cluster DevFeed: [June Update: postmarketOS CE PinePhone, Shipping & PINE64 Cluster]() Original publisher: [Read original article]() Published: 2020-06-15T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone](), [Hardware](), [IRC](), [Matrix](), [modules]() Tags: [cluster](), [debian](), [hardware](), [irc](), [matrix](), [modules](), [pine64](), [pinephone](), [pinetab](), [pinetime](), [postmarketos](), [progress-report](), [update]() ### AI overview PINE64's June 2020 update covers the planned postmarketOS Community Edition PinePhone pre-order, PineTab and Pinebook Pro shipping matters, PineTime, power-management work, and related community projects. It also reports that PINE64 migrated its community services to a cluster of 24 ROCKPro64 computers running Debian. ### Source excerpt Hello everyone! It has been a really busy time for us here at PINE64 as we're working hard to deliver outstanding PinePhone UBports Community Edition and Pinebook Pro shipments. The big news of this month is that we're excited to announce that a postmarketOS Community Edition PinePhone will be available for pre-order early next month. There are a lot of topics to cover this month, so let's get to it. This month's TL;DR All PINE64 services on our own hardware; the cluster move report Shipping delays and Pinebook Pro QA issues addressed Shipping status update & where to find up-to-date information An apology for PineTab pre-orders delay & no heads-up on blog PineTab pre-orders sold out in under 72 hours PineTab to ship late July 2020; more batches coming PineTab add-on board reengineered for LoRa and RTL-SDR modules; available for next pre-order batch PinePhone postmarketOS Community Edition announcement; pre-orders start early July Check out postmarketOS announcement blog post! PinePhone CRUST advanced power management status A community initiative; a PinePhone pogo pin breakout board PineTime; Lup Yuen Lee will write a series of PineTime articles for our blog! Solve the riddle! Housekeeping We're proud to announce that starting this month all our community services, including this very website you're currently visiting, are all running on our PINE64 cluster of 24x ROCKPro64 single board computers. The process of migrating services to the cluster began on June 5 and finished on the 10th without any major dowtimes or hiccups. As of right now the cluster hosts the main PINE64 website, the Wiki, forum, IRC server (and chat bridge) as well as all our Matrix channels. To our knowledge we're the only organization in this neck of the woods to dogfood hardware in this way. I like when things speak for themselves, and so I hope and trust that this is a testimony to our faith in our own hardware. I know many of you are very keen to learn more about the cluster, so I already ha ## ROCKPro64 Cluster Move June 5-10 DevFeed: [ROCKPro64 Cluster Move June 5-10]() Original publisher: [Read original article]() Published: 2020-06-05T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Server](), [maintenance](), [IRC](), [Wiki](), [Website]() Tags: [cluster](), [community](), [forum](), [infrastructure](), [irc](), [maintenance](), [pine64](), [rockpro64](), [server](), [website](), [wiki]() ### AI overview PINE64 announces a June 5-10 move of end-user services to the ROCKPro64 cluster. The forum, Wiki, chat bridge, IRC, parts of the support system, installer mirrors, and website may experience downtime, while the store, ticket filing system, and support emails are expected to remain operational. An update reports that the key community infrastructure was moved successfully by June 11, 2020. ### Source excerpt The process of moving our end-user services to the ROCKPro64 cluster will be taking place in the coming days (5-10 June). I am not going to pretend like this is the best time for the move to be taking place, since it is not. Many users are relying on our infrastructure for information and community support, particular now that people are receiving their devices and many more are waiting for their units to ship. But things are what they are, and we have a strict deadline we need to adhere to. In practice, this means that at different times during this move key parts of the infrastructure will be down. This includes: the forum, the Wiki, the chats bridge and IRC, portions of the support system, PINE Installer mirrors as well as this website. It is not possible for me to say with certainty when exactly each of these community-facing services will be moved nor how long it will be down for. Obviously we'll aim to complete the process as quickly and painlessly as possible but unpredictable things can, and likely will, happen. I'll do my best to give you a heads-up when portions of the system are scheduled to go down for maintenance on Twitter and Mastodon. I'll also issue notices in the news section of the forums. Lastly, I'd like to note that the PINE store and ticket filing system, as well as our info and support emails will remain operational though the entire server move. Thank you in advance for your patience. [edit June 11, 2020] All key community based infrastructure has now been moved to the cluster. Moreover, the move went went surprisingly well and without any major hiccup. In the coming weeks and months we'll be adding more services to the cluster. I have already spoken to FireTwoOneNine about writing a short blog post about the cluster, its present utilization and future applications in the project. Lastly, I'd like to thank all those who offered advise and were directly involved in this project. ## Leader Election inside Kubernetes DevFeed: [Leader Election inside Kubernetes]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2020-03-14T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Kubernetes](), [Go](), [API](), [Deployment]() Tags: [cluster](), [docker](), [github](), [go](), [kubernetes](), [leader](), [leader-election](), [rbac]() ### AI overview A tutorial on implementing leader election for applications running on Kubernetes. It uses Kubernetes' leader election package from the Go SDK, explains pod-based identity and lease management, and covers the RBAC permissions required for the deployment. ### Source excerpt Ever needed a simple leader election mechanism on something that will run on a Kubernetes cluster? There's an easy way to do that! ## November Update: Brave Heart, Pinebook Pro reception and more DevFeed: [November Update: Brave Heart, Pinebook Pro reception and more]() Original publisher: [Read original article]() Published: 2019-11-05T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone](), [Hardware](), [Software](), [Development]() Tags: [cluster](), [hardware](), [keyboard](), [nvme](), [pinebook-pro](), [pinephone](), [pinetime](), [rockpro64](), [software](), [update]() ### AI overview PINE64's November community update covers shipping progress for the Pinebook Pro, PinePhone developer edition, and PineTime development kits. It announces PinePhone Brave Heart pre-orders and another Pinebook Pro pre-order run, while also discussing planned infrastructure migration and reported hardware issues. ### Source excerpt Our core focus for the past month was on getting the manufacturing process and shipping of the Pinebook Pro, PinePhone and PineTime development kits back on track. I will not reiterate the events that led to the delays of those devices in this post, but if you're interested then read the detailed account of what happened in last month's community update. With the Pinebook Pros and PineTime development kits now shipped, and with the PinePhone developer edition now shipping, I feel that we've done a good job in handling the situation. The big news for this month is that we will start taking pre-orders for the PinePhone Brave Heart edition on November 15 and that the next Pinebook Pro production-run pre-orders, offering a choice of ANSI or ISO keyboard, starts today. Let's get to it. [update 19/11/2019] I have now posted a follow-up to this community update on the forum; mostly containing information about the PineTime dev kits and PineTab availability based on your feedback. It can be read here. Here's the TL;DR: Our monster clusters; core community services will migrate to our own hardware in 2020 Pinebook Pros shipped; Last pre-orders for ~3 months start today (ANSI +ISO) We're aware of NVMe adapter & Trackpad issues, expect fixes soon OG Pinebook upgrade to Pro-esque setup in Q1 2020 PinePhones for developers (finally) ship November 5-18th PinePhone Brave Heart Pre-Orders start November 15th; delivery December 2019 / January 2020 PineTab production conundrum; state of software PineTime dev kits shipped; development proceeding exceptionally well Housekeeping Earlier this year we announced that we've built two monster ROCKPro64 clusters with the intention to host our website, Wiki, forums, CDN, Matrix instance, IRC, etc., as well as provide the community with an efficient OS images build server. We've have since been looking for a reliable host that would meet our criteria in terms of support, bandwidth, services and access that could house the server. Thanks to Gami ## 即刻多端实时通信实践 DevFeed: [即刻多端实时通信实践]() Original publisher: [Read original article]() Author: Joway Published: 2018-09-18T00:00:00Z Content type: article Language: zh Sources: [Random Thoughts]() Topics: [Socket.IO](), [WebSocket](), [Redis](), [Load Balancing](), [Back end](), [Publish-subscribe pattern]() Tags: [backend](), [channel](), [clients](), [cluster](), [load-balancing](), [nodejs](), [redis](), [room](), [socket](), [tech](), [websocket]() ### AI overview This Chinese technical article explains how Jike's jike-io real-time communication infrastructure is built with socket.io. It describes server-to-client WebSocket notifications, per-user rooms, HTTP requests for business operations, socket.io's fallback and reconnection behavior, and Redis-based distribution across nodes, including sticky load balancing and the associated message-broadcast overhead. It also discusses connection spikes and Node.js bottlenecks. ### Source excerpt 背景 jike-io 是即刻基于 socket.io 构建的一个实时通信基础设施。目前客户端上的所有实时通信服务都是建立在其基础上，涵盖了私信、消息通知、用户反馈、活动页小游戏等诸多组件。 在目前即刻的实时通信设计里，我们的实时通信只是为了让服务端主动推送消息给客户端，客户端不会主动通过 websocket 发送消息。由于几乎我们所有需要发送消息的请求都会有一定业务逻辑在，而这个业务逻辑我们并不希望 websocket 连接层(jike-io)去处理，所以我们仍旧采用传统 HTTP 请求的方式去发送请求。至于之后是否需要推送消息给用户，由服务端调用 jike-io 的接口进行实现。 ## OSCON DevFeed: [OSCON]() Original publisher: [Read original article]() Published: 2013-07-24T22:00:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [migration](), [PostgreSQL](), [postgresql clusters](), [MySQL](), [PHP](), [Java](), [Availability](), [Load Balancing]() Tags: [availability](), [cluster](), [high-availability](), [java](), [load-balancing](), [migration](), [mysql](), [php](), [postgresql]() ### AI overview A technical presentation describes migrating a complex system and architecture from MySQL and Java to PostgreSQL and PHP, including the context and trade-offs involved. It also describes a 16-node PostgreSQL cluster with high availability and read/write load balancing. ### Source excerpt The migration of a complex system and architecture from MySQL and Java to PostgreSQL and PHP, with plenty details about the context and the trade-offs that were made in the process. Also, full description of a PostgreSQL Cluster of 16-nodes, with High-Availability and Read and Write Load-Balancing implemented. ## Scaling Stored Procedures DevFeed: [Scaling Stored Procedures]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-10-06T16:23:00Z Content type: opinion Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Scalability](), [postgresql clusters](), [Architecture & Design]() Tags: [api](), [cluster](), [database](), [postgresql](), [scalability](), [stored-procedures](), [upgrade](), [version]() ### AI overview The article argues that stored procedures do not inherently prevent database scalability. It describes PostgreSQL Extensions for managing procedure code and versions, and PLproxy for scaling out across database shards with a shared procedural API. ### Source excerpt In the news recently stored procedures where used as an excuse for moving away logic from the database layer to application layer, and to migrate away from a powerful technology to a simpler one, now that there's no logic anymore in the database. It's not the way I would typically approach scaling problems, and apparently I'm not alone on the Stored Procedures camp. Did you read this nice blog post Mythbusters: Stored Procedures Edition already? Well it happens in another land that where my comfort zone is, but still has some interesting things to say. ## PostgreSQL replication solutions discussed at CHAR(11) DevFeed: [PostgreSQL replication solutions discussed at CHAR(11)]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-07-13T15:30:00Z Content type: opinion Language: fr Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Replication](), [Streaming](), [postgresql clusters]() Tags: [architecture](), [cluster](), [failover](), [postgresql](), [replication](), [standby](), [streaming]() ### AI overview A report from CHAR(11) discusses the history and evolution of PostgreSQL replication solutions, comparing Skytools, Slony, and PostgreSQL's integrated Streaming Replication and Hot Standby. It also describes synchronous replication in PostgreSQL 9.1 and repmgr features for cluster administration, read-load distribution, and automatic failover. ### Source excerpt Quelle meilleure occupation dans le train du retour de CHAR(11) que de se faire reporteur pour l'occasion ? En réalité, dormir serait une idée tant les soirées se sont prolongées ! Nous avons eu le plaisir d'écouter Jan Wieck présenter un historique simplifié de la réplication avec PostgreSQL. Étant lui-même l'un des pionniers du domaine, son point de vue est des plus intéressants. Il a parlé de l'évolution des solutions de réplication, et je ne peux m'empêcher de penser que par bien des côtés Skytools est une évolution de Slony -- Jan, auteur de Slony, semblait d'accord avec cela. ## Why you need a cluster DevFeed: [Why you need a cluster]() Original publisher: [Read original article]() Author: Graham King Published: 2006-02-16T13:37:24Z Content type: opinion Language: en Sources: [Graham King]() Topics: [web applications](), [sticky sessions](), [proxy](), [backends](), [Security](), [reliability]() Tags: [back-end](), [cluster](), [clustering](), [maintenance](), [proxy](), [release](), [security](), [software](), [sticky-sessions](), [web-applications]() ### AI overview The article argues that live web applications with more than a few geographically separated users should use a cluster primarily for easier upgrades and maintenance, rather than performance or reliability. It describes a public dispatcher proxying requests to multiple back-end servers, sticky sessions, and operational benefits such as testing releases on an isolated server and limiting direct external access. ### Source excerpt Cluster for better manageability.