fsyncDATA

Networking: the GCC database peer network

Most networking is a lanyard and a queue for coffee. Here it is a set of mechanisms, each run by the secretariat, each designed so that the right person picks up the phone.

The network is organised by engine first and by role second, so that a DBA with a lagging replica reaches someone who has fixed that lag on that engine, and a CDO with a renewal reaches someone who has negotiated it.

Seven mechanisms

48 hours

The peer bench

Post a question; it goes to three members who run that engine at comparable scale. Answers within 48 hours, and they stay inside the club.

Quarterly

City chapters

Bengaluru, Hyderabad, Pune and Chennai. An evening each quarter, by guild or mixed, with no talk longer than ten minutes.

First month

Warm introductions

Three in your first month, each with a reason, and on request after that.

Ongoing

Center-and-parent pairing

Members at a GCC paired with members in a parent’s data organisation, so each side hears what the other cannot say at work.

Deep dives

Cross-tier tables

Circle members seated beside the guild members who operate what is being decided.

Members only

The directory

Name, role, engines, city and sector. Never exported, never shared, never used to sell.

With consent

Successor visibility

Senior members can see which guild members are ready for a bigger estate. Membership is personal, so it moves with them.

Apply, ask, or nominate someone better

Practitioners apply to a Guild. Leaders request a Circle invitation. Anyone may nominate a peer. Every message to the secretariat is answered by a person within two working days.