Two way streams for your microservices
Project description
2-way streams for your microservices
What is a stream with feedbacks?
With Streamback you can implement the producer-consumer model but with a twist. The consumer can send feedback messages back to the producer via a feedback stream, making it work more like an RPC than the one way stream Kafka is intended to be used as.
How it works?
Streamback implements two different streams, the main stream and the feedback stream.
- Main stream: This is the kafka stream that the producer sends messages to the consumer.
- Feedback stream: This is the stream that the consumer sends messages to the producer. Redis is used for this stream for its
- simplicity and speed.
Why not just use the conventional one way streams?
Streamback does not stop you from just using the main stream and not sending feedback messages, this way it is behaving just like a Kafka producer-consumer. Streamback just gives you the option to do so if you need it in order to make more simple the communication between your microservices.
Installation
pip install streamback
Examples
One way stream consumer-producer
Consumer
from streamback import Streamback
streamback = Streamback(
"example_consumer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379"
)
@streamback.listen("test_hello")
def test_hello(context, message):
print("received: {value}".format(value=message.value))
streamback.start()
Producer
from streamback import Streamback
streamback = Streamback(
"example_producer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379"
)
streamback.send("test_hello", {"something":"Hello world!"})
2-way RPC like communication
Consumer
from streamback import Streamback
streamback = Streamback(
"example_consumer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379"
)
@streamback.listen("test_hello_stream")
def test_hello_stream(context, message):
print("received: {value}".format(value=message.value))
message.respond("Hello from the consumer!")
streamback.start()
Producer
from streamback import Streamback
streamback = Streamback(
"example_producer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379"
)
message = streamback.send("test_hello_stream", {"something":"Hello world!"}).read(timeout=10)
print(message)
2-way RPC like communication with steaming feedback messages
Consumer
from streamback import Streamback, KafkaStream, RedisStream
import time
streamback = Streamback(
"example_consumer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379"
)
@streamback.listen("test_hello_stream")
def test_hello_stream(context, message):
print("received: {value}".format(value=message.value))
for i in range(10):
message.respond("Hello #{i} from the consumer!".format(i=i))
time.sleep(2)
streamback.start()
Producer
from streamback import Streamback
streamback = Streamback(
"example_producer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379"
)
for message in streamback.send("test_hello_stream", {"something":"Hello world!"}).stream():
print(message)
## OR
stream = streamback.send("test_hello_stream", {"something":"Hello world!"})
message1 = stream.read()
message2 = stream.read()
message3 = stream.read()
Consumer input mapping to objects
For a more type oriented approach you can map the input of the consumer to a class.
class TestInput(object):
def __init__(self, arg1, arg2):
self.arg1 = arg1
self.arg2 = arg2
@streamback.listen("test_input")
def test_input(context, message):
input = message.map(TestInput)
print(input.arg1)
print(input.arg2)
message.respond({
"arg1": input.arg1,
"arg2": input.arg2
})
Producer feedback mapping to objects
In a similar way you can map the feedback of the producer to a class.
class TestResponse(object):
def __init__(self, arg1, arg2):
self.arg1 = arg1
self.arg2 = arg2
response = streamback.send("test_input", {"arg1": "Hello world!", "arg2": "Hello world!"}).read("main_app",
map=TestResponse)
print(response.arg1)
print(response.arg2)
Input injection
Instead of having to deconstruct the message.value inside the consumer's logic, you can pass to the consumer only the arguments of the message.value that you want to use.
@streamback.listen("test_input", input = ["arg1", "arg2"])
def test_input(arg1, arg2):
pass
streamback.send("test_input", {"arg1":"Hello world!", "arg2": "Hello world!"})
Class based consumers
@streamback.listen("new_log")
class LogsConsumer(Listener):
logs = []
def consume(self, context, message):
self.logs.append(message.value)
if len(self.logs) > 100:
self.flush_logs()
def flush_logs(self):
database_commit(self.logs)
Router
The StreambackRouter helps with spliting the consumer logic into different files, it is not required to use it but it helps
some_consumers.py
from streamback import Router
router = Router()
@router.listen("test_hello")
def test_hello(context, message):
print("received: {value}".format(value=message.value))
my_consumer_app.py
from streamback import Streamback
from some_consumers import router as some_consumers_router
streamback = Streamback(
"example_consumer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379"
)
streamback.include_router(some_consumers_router)
streamback.start()
Handling consume exceptions
You can pass the on_exception callback upon creating the Streamback object to handle exceptions that occur during the consumption of messages by the listeners
from streamback import Streamback
def on_exception(listener, context, message, exception):
print("on_exception:", listener, context, message, exception)
streamback = Streamback(
"example_consumer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379",
on_exception=on_exception
)
from streamback import Streamback
def on_exception(listener, context, message, exception):
print("on_exception:", listener, context, message, exception)
streamback = Streamback(
"example_consumer_app",
streams="main=kafka://kafka:9092&feedback=redis://redis:6379",
on_exception=on_exception
)
Why python 2.7 compatible?
Streamback has been created for usage in car.gr's systems which has some legacy python 2.7 services. We are are planing to move Streamback to python >3.7 in some later version but for now the python 2.7 support was crucial and thus the async/await support was sacrificed.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file streamback-0.0.37.tar.gz.
File metadata
- Download URL: streamback-0.0.37.tar.gz
- Upload date:
- Size: 15.1 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.2 CPython/3.9.5
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
d8d2b7097b85db726096b939cb2a916bbb31db9ede8fd8f34c7340a4a327e91c
|
|
| MD5 |
df67c7f084fd3e2751e80c3477e797d3
|
|
| BLAKE2b-256 |
cb1ca4f73029d1516450b445f5f992c292f09a917255a43189ab83208b8f69e6
|
File details
Details for the file streamback-0.0.37-py3-none-any.whl.
File metadata
- Download URL: streamback-0.0.37-py3-none-any.whl
- Upload date:
- Size: 16.2 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.2 CPython/3.9.5
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6a572647cf8f68613954bb597a9b46f51ea54446f68c79e9862171d024cf4f4f
|
|
| MD5 |
6fe81cc89434f3f18045c287c9087858
|
|
| BLAKE2b-256 |
b9bab412e0f7eaa53c0614b8cb608f832c7326d02e0cd995667449b8b78e129d
|