[Verse 1]
When legacy systems need to talk to streams
And REST APIs fulfill your dreams
Deploy the Bridge with a simple CRD
HTTP to Kafka, seamlessly
KafkaBridge custom resource you define
Replicas and bootstrap servers align
Port eight zero eight zero opens the door
RESTful messaging like never before
[Chorus]
Bridge the gap, REST to streams
HTTP calls fulfill your dreams
Post to topics, get from queues
Legacy systems, serverless too
Bridge the gap, make it flow
Kafka Bridge is the way to go
[Verse 2]
Producing messages through HTTP POST
Content type JSON is what you need most
Topics endpoint takes your payload in
Consumer groups let the reading begin
IoT devices send their sensor data
Serverless functions process metadata
No native client libraries required
Just simple REST calls as desired
[Chorus]
Bridge the gap, REST to streams
HTTP calls fulfill your dreams
Post to topics, get from queues
Legacy systems, serverless too
Bridge the gap, make it flow
Kafka Bridge is the way to go
[Bridge]
But remember the performance cost
Native clients won't be lost
HTTP overhead adds delay
For high throughput, consider the native way
Stateless bridge means no consumer state
Long polling helps but don't be late
Scale your bridge pods when traffic grows
Monitor metrics, watch how it flows
[Verse 3]
Use cases span from web to cloud
Integration patterns, flexible and proud
REST microservices join the stream
Kafka Bridge completes the team
Configure cors for browser calls
Enable metrics to monitor it all
Authentication and authorization too
Security features see you through
[Chorus]
Bridge the gap, REST to streams
HTTP calls fulfill your dreams
Post to topics, get from queues
Legacy systems, serverless too
Bridge the gap, make it flow
Kafka Bridge is the way to go
[Outro]
From CRD deploy to REST API
Kafka Bridge lifts your systems high
HTTP to streams, the bridge you need
Strimzi makes integration succeed