Replace REST and RabbitMQ with gRPC#175
Replace REST and RabbitMQ with gRPC#175benthecarman wants to merge 1 commit intolightningdevkit:mainfrom
Conversation
|
🎉 This PR is now ready for review! |
benthecarman
force-pushed
the
grpc
branch
6 times, most recently
from
c99b7a3 to
f176109
Compare
Consolidate the two separate communication protocols (protobuf over REST via Hyper, and RabbitMQ for events) into a single gRPC interface using tonic. This eliminates the RabbitMQ operational dependency and gives clients strongly-typed generated stubs. Events are now delivered via a server-streaming RPC backed by a tokio broadcast channel. HMAC auth moves to a tonic interceptor using timestamp-only signing since TLS guarantees body integrity. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
🔔 1st Reminder Hey @tnull @joostjager! This PR has been waiting for your review. |
1 similar comment
|
🔔 1st Reminder Hey @tnull @joostjager! This PR has been waiting for your review. |
|
🔔 2nd Reminder Hey @tnull @joostjager! This PR has been waiting for your review. |
1 similar comment
|
🔔 2nd Reminder Hey @tnull @joostjager! This PR has been waiting for your review. |
|
closing in favor of #176 |
2 participants
Alternative to #168, wanted to quickly see what this would look like
Consolidate the two separate communication protocols (protobuf over REST via Hyper, and RabbitMQ for events) into a single gRPC interface using tonic. This eliminates the RabbitMQ operational dependency and gives clients strongly-typed generated stubs.
Events are now delivered via a server-streaming RPC backed by a tokio broadcast channel. HMAC auth moves to a tonic interceptor using timestamp-only signing since TLS guarantees body integrity.