PostgreSQL Cluster: “Too Many Projects” problem

“Too Many Projects” problem

The “too many projects” problem of PostgreSQL Cluster was raised and discussed in the PostgreSQL Clustering Developer Meeting at the JPUG Conference.

Nowadays, the PostgreSQL developer community has many clustering/replication projects, but many of them are not production ready. Though, new project is starting, and old project is still unmature.

I think this is one of the biggest challenges of the OpenSource development community.

Why happens this? How can we solve this, and get solutions mature?

Back to the OpenSource world

Finally, I’m back to the OpenSource world.

In 2004, I started working as a PostgreSQL developer and database engineer. While I was working as a PostgreSQL engineer, I was joining several PostgreSQL cluster projects, including Slony-II. Unfortunately, some were not happen, but it gave me great experiences.

At the same time, I was working as a director of Japan PostgreSQL Users Group (JPUG), and planned and run several community events such as JPUG conferences, camps and study groups. I was enjoying meeting with technical and non-technical people around PostgreSQL in Japan.

After a few years working as a PostgreSQL engineer, I moved to the datacenter business division in Oct.2007, and started working as a business developer of the datacenter services. It was very exciting to look for the market in the datacenter and cloud boom.