Content
@
0 reply
0 recast
0 reaction
christopher
@christopher
In December, we replaced @farcaster/shuttle with Waypoint, our custom event processing system built with Rust, protobufs, and sqlx. It's very fast and much more memory efficient. Running on an optimized Kubernetes cluster with Terraform infrastructure, it also requires minimal costs and delivers instant upgrades. This change addressed memory leaks and reliability issues with Farcaster hubs and shuttle containers, while reducing our support dependency on Merkle as they pivot focus to Snapchain development. Our architecture also leverages GCP's managed services like PubSub and Cloud SQL/Bigtable for more coherent data systems. Waypoint will be open-sourced as an app and lib soon so anyone can run their own internal protocol data services. DM me directly to contribute to early development. Below is our Farcaster cluster slowly eating up memory and resources, causing disruptions in event subscriptions as it randomly restarts to heal.
5 replies
10 recasts
34 reactions
Samuel ツ
@samuellhuber.eth
How can I be of value ? Would love to provide any value I can! Love this! Cc @leewardbound seems like there’s a better system we should write a helm chart for then the Hubs (btw helm chart for hubs still works)
1 reply
0 recast
2 reactions
christopher
@christopher
TF will just provision the k8s cluster and core infrastructure, but yeah you could use Helm to deploy and manage Waypoint and whatever other apps within that cluster. Will reach out later to test the open source package 👍
0 reply
0 recast
0 reaction
