Why it existed
Hub gRPC streaming delivers dehydrated events that you have to reassemble yourself to make useful (see here for example). The Kafka stream delivered a fully hydrated event (e.g., user.created) that was usable immediately. The comparison between a gRPC hub event and a Kafka event is below. Webhooks deliver these same hydrated events and are the supported way to get them today.
How it worked
The connection details, brokers and topics below are recorded as they were at shutdown. None of them accept connections any more.
- Authentication used
SASL/SCRAM SHA512. - The connection required TLS (sometimes called SSL for legacy reasons) for encryption.
farcaster-mainnet-eventswas the aggregated topic containing all events.farcaster-mainnet-user-eventscarrieduser.created,user.updatedanduser.transferredfarcaster-mainnet-cast-eventscarriedcast.createdandcast.deletedfarcaster-mainnet-follow-eventscarriedfollow.createdandfollow.deletedfarcaster-mainnet-reaction-eventscarriedreaction.createdandreaction.deletedfarcaster-mainnet-signer-eventscarriedsigner.createdandsigner.deleted
farcaster-mainnet-events to get everything in one topic.
Three brokers were exposed over the Internet, and clients were given all three:
b-1-public.tfmskneynar.5vlahy.c11.kafka.us-east-1.amazonaws.com:9196b-2-public.tfmskneynar.5vlahy.c11.kafka.us-east-1.amazonaws.com:9196b-3-public.tfmskneynar.5vlahy.c11.kafka.us-east-1.amazonaws.com:9196
kcat (formerly kafkacat) was used to test connectivity locally: