Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Eventstore Client Bundle Laravel Package

dbellettini/eventstore-client-bundle

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Event Sourcing Architecture: Enables adoption of event-driven design patterns for auditability, replayability, and scalability in Symfony applications.
  • KurrentDB Integration: Facilitates seamless migration or integration with KurrentDB (a PostgreSQL-based event store) for teams already using or evaluating PostgreSQL-based event storage solutions.
  • Symfony 7.3+ Compatibility: Aligns with modern Symfony ecosystems, reducing friction for teams upgrading or maintaining newer versions.
  • Build vs. Buy: Avoids reinventing event store client logic, accelerating time-to-market for event-driven features.
  • Use Cases:
    • Financial systems requiring immutable audit logs.
    • E-commerce platforms needing order history replayability.
    • Real-time analytics or CQRS implementations.

When to Consider This Package

  • Adopt if:

    • Your team uses Symfony 7.3+ and needs event sourcing with KurrentDB.
    • You prioritize PostgreSQL-based event storage over alternatives like EventStoreDB or custom solutions.
    • Your roadmap includes event-driven architecture (e.g., CQRS, sagas, or audit trails).
    • You want to reduce boilerplate for event store operations (e.g., appending, querying, or subscribing to events).
  • Look elsewhere if:

    • You’re not using Symfony (package is framework-specific).
    • Your event store is not KurrentDB (e.g., EventStoreDB, MongoDB, or custom SQL).
    • You need multi-language support (this is PHP-only).
    • The package’s low adoption (3 stars) raises concerns about long-term maintenance or community support.
    • You require advanced features (e.g., gRPC, custom serialization) not covered in the bundle.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us leverage KurrentDB’s event sourcing capabilities natively in Symfony, cutting development time for audit logs, order history, or real-time systems. It’s a lightweight, MIT-licensed solution that aligns with our PostgreSQL stack and modern Symfony investments. Low risk, high reward for event-driven features."

For Engineering: "The eventstore-client-bundle provides a Symfony-friendly wrapper for KurrentDB, handling event appending, querying, and subscriptions with minimal setup. It’s ideal if we’re using KurrentDB and want to avoid reinventing event store clients. However, its niche focus (Symfony + KurrentDB) and low stars mean we should validate KurrentDB’s fit first. Prototype with a single use case (e.g., order events) before full adoption."

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
tequilarapido/trackit
gregsphotography/site-builder-filament
cabaoctavio/laravel-query-log
gregsphotography/site-builder-components
io-digital/clickatell
snowsoft/laravel-admin
oxygen/auth
relicsoftware/barakah-payment-gateway
tobya/work-with-composer
equipc/laravel-email-validator
equipc/laravel-email-database-log
adedsec/nova-translated-labels
wazza/laravel-db-encryption
hokny/laravel-generator
vonsogt/backup
jengo/queues
jeremykenedy/laravel-observability
coleus/frame
thtg88/journalism
filagora/filagora-ai-forums