Eventiq
Welcome to eventiq documentation
Cloud native, event driven microservice framework for python
Note: This package is under active development and is not recommended for production usage
Version: 0.2.0
Documentation: https://performancemedia.github.io/eventiq/
Repository: https://github.com/performancemedia/eventiq
About
The package utilizes anyio
and pydantic
as the only required dependencies.
For messages Cloud Events format is used.
Service can be run as standalone processes, or included into starlette (e.g. FastAPI) applications.
Installation
Multiple brokers support
- Stub (in memory using
asyncio.Queue
for PoC, local development and testing) - NATS (with JetStream)
- Redis Pub/Sub
- Kafka
- Rabbitmq
- Google Cloud PubSub
- And more coming...
Optional Dependencies
cli
-typer
- broker of choice:
nats
,kafka
,rabbitmq
,redis
,pubsub
- custom message serializers:
msgpack
,orjson
prometheus
- Metric exposure viaPrometheusMiddleware
opentelemetry
- Tracing support
Motivation
Python has many "worker-queue" libraries and frameworks, such as:
However, those libraries don't provide a pub/sub pattern, useful for creating
event driven and loosely coupled systems. Furthermore, the majority of those libraries
do not support asyncio
. This is why this project was born.
Basic usage
import asyncio
from eventiq import Service, CloudEvent, Middleware
from eventiq.backends.nats.broker import JetStreamBroker
class SendMessageMiddleware(Middleware):
async def after_broker_connect(self, broker: "Broker") -> None:
print(f"After service start, running with {broker}")
await asyncio.sleep(10)
for i in range(100):
await broker.publish("test.topic", data={"counter": i})
print("Published event(s)")
broker = JetStreamBroker(url="nats://localhost:4222")
broker.add_middleware(SendMessageMiddleware())
service = Service(name="example-service", broker=broker)
@service.subscribe("test.topic")
async def example_run(message: CloudEvent):
print(f"Received Message {message.id} with data: {message.data}")
if __name__ == "__main__":
service.run()
Scaling
Each message is load-balanced (depending on broker) between all service instances with the same name
.
To scale number of processes you can use containers (docker/k8s), supervisor,
or web server like gunicorn.