Skip to main content

Cloud native framework for building event driven applications in Python

Tests Build License Python Format PyPi Code Style security: bandit

Note: This package is under active development and is not recommended for production use

|Version|0.1.1| |Documentation| |--|---|---|


Version: 0.1.2

Documentation: https://performancemedia.github.io/eventiq/

Repository: https://github.com/performancemedia/eventiq


About

The package utilizes pydantic, async_timeout and python-json-logger 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

pip install eventiq

Multiple broker support (in progress)

  • 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 comming

Optional Dependencies

  • cli - typer and aiorun
  • broker of choice: nats, kafka, rabbitmq, redis, pubsub
  • custom message serializers: msgpack, orjson
  • prometheus - Metric exposure via PrometheusMiddleware

Motivation

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.

TODOS:

  • More tests
    • Integration tests with docker-compose and all backends
  • Docs + tutorials
  • OpenTelemetry Middleware (?)

Metadata

Release files for eventiq 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eventiq 0.1.2
File Size Uploaded Provenance Actions
eventiq-0.1.2.tar.gz 29.3 kB Without provenance Details for eventiq-0.1.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for eventiq 0.1.2
File Interpreter ABI Platform Actions
eventiq-0.1.2-py3-none-any.whl Python 3 none any Details for eventiq-0.1.2-py3-none-any.whl

Total release size: 74.7 kB

Release files / eventiq-0.1.2.tar.gz

Download URL eventiq-0.1.2.tar.gz
Size 29.3 kB
Tags Source
SHA-256 checksum
How to use checksums
6b474601bf4658ac4018d898b5800bf584abfc19594c9eb8b36a6f94c8179023
BLAKE2b-256 checksum
How to use checksums
4f4a7cac0ec2889b9a00ed645499df6fefda07f4c67520bd61b60241153135d0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.9.16

Release files / eventiq-0.1.2-py3-none-any.whl

Download URL eventiq-0.1.2-py3-none-any.whl
Size 45.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f19b8bba6cefb58f80366e89a55c129bc587cbb5385bec12bc9dcd218f18844e
BLAKE2b-256 checksum
How to use checksums
025534448d2edd1de3cc0f177d4bad6e0050e8b016953a3e8a8dbff9d4e63bdd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.9.16

Security for eventiq 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page