What we covered
Most of the engineering in a Web3 product is not on-chain. It is the system that watches the chain, absorbs bursts, and answers queries fast enough to feel like a normal app. That system is what we build.
- The Web3 challenge stated plainly, and where cloud infrastructure is the answer to it.
- Listening to the chain with Infura, and what happens when the feed hiccups.
- Decoupling ingestion from processing with Pub/Sub, so a burst on-chain doesn't take the app down.
- Workers and caching: turning a stream of raw events into something queryable.
- Choosing the right Google Cloud database for the access patterns you actually have.
- A Kubernetes-based architecture on GKE, and how to split the backend across it.
- The other GCP services worth knowing about before you build around their absence.
Format
A workshop that follows one architecture from the chain listener through to the serving layer, with the trade-off at each hop made explicit.
Who it's for
Backend engineers and architects building on-chain-adjacent products who want the infrastructure design settled before the contract work starts.