EcotoneFramework retweeted
CQRS. Async processing with retries and dead-lettering. Event sourcing with projections. Workflows. Delayed messages. Outbox. Multi-tenancy.
All of it runs on Tempest now. The setup is one line:
composer require ecotone/tempest
No config file, no service provider.

ALT Layered diagram titled "Tempest + Ecotone — how the integration works": bottom layer, application level, Tempest (container, discovery, database models, HTTP, views, authentication) installed with composer require tempest/framework; middle layer, architecture level, Ecotone (durable messaging, asynchronous processing, failure recoverability, event sourcing, workflow engine) installed with composer require ecotone/tempest; top layer, business logic — aggregates, command/event/query handlers, projections, workflows as plain PHP classes with attributes — labelled "this is what you write"
EcotoneFramework retweeted
Most scaling discussions about event-sourced projections start with resources.
To me, they should start with the projecting model itself.
If the design doesn't allow scaling, hardware doesn't move the wall.
Wrote up the model we applied in Ecotone. Article already available for free members of blog.ecotone.tech
blog.ecotone.tech/when-one-w…
EcotoneFramework retweeted
Most projection articles talk about the happy path.
But that is usually not where teams struggle.
They struggle:
- When a projection crashes on one bad event.
- When a read model bug blocks a valid business operation.
- When catch-up runs eat memory and lock tables for too long.
And when recovery means manual resets, replay scripts, and stress at 3 AM.
"Your Projection Will Fail" article is about those problems. I wrote it to show how resilient projections should actually work:
- How to isolate projection failures from the command side
- How to make projections self-heal after a fix
- How protects you from memory and transaction issues
So if you have ever dealt with projections that were fragile, blocking, or painful to recover, this is for you.
EcotoneFramework retweeted
Your projections will fail.
The real question is what happens next.
Do they recover after a fix?
Do they block valid business operations?
Do they turn catch-up into operational pain?
That’s what this article is about.
Available now on blog.ecotone.tech with a free account.
Public release on Tuesday.
#php #ddd #eventsourcing #cqrs
EcotoneFramework retweeted
Jean (main co-maintainer) and I have been rebuilding the Event Projecting System in Ecotone from scratch — replacing the Prooph-based engine.
Today it's public, along with a 5-part article series:
→ Track-based gap detection (no more silent data loss)
→ Self-healing projections
→ Partitioned scaling
→ Event emission from read models
→ Blue-green deployments
I've written one article per topic, new one every week starting today. The articles go deep on internals and patterns — useful whether you use Ecotone or not.
▎ Article 1 is live on blog.ecotone.tech. New one every week. Register on the platform for free - to get the next article early.
EcotoneFramework retweeted
"Commands belong to the Application Layer" is the most repeated DDD rule that nobody stops to question.
Let's think about it differently.
Commands are actions we want to perform. Events are results of actions taken. Two sides of the same pipe. Events follow business language ("OrderWasPlaced") — so why don't Commands? "PlaceOrder" IS business language. It IS a domain concept.
Now remember what Alan Kay meant by OOP: all communication happens through Messages. Commands are Messages. Aggregates are transaction boundaries — our entrypoints.
If communication happens through Messages, and Aggregates are entrypoints... Command Handlers are just business actions on Aggregates. They map 1:1.
So why do we write 50 identical handler classes that all do: load aggregate, call method, save, publish events?
That's not application logic. That's infrastructure. The framework should own it.
With Ecotone:
```php
#[Aggregate]
class Order
{
#[CommandHandler]
public static function create(CreateOrder $command): self
{
// just business logic here
}
}
```
No Application Layer. No handler classes. The Command maps directly from HTTP — no Request -> DTO -> Command chain. No re-mapping means no problems.
To add new business logic: method on Aggregate + Controller action. Done. Simpler than CRUD.
The problem was never DDD. It was treating guidelines as laws and building ceremony instead of business logic.
EcotoneFramework retweeted
AI writes code 55% faster.
AI-generated code has 41% higher churn rate.
The difference? What patterns AI has to follow.
@EcotonePHP @AxonFramework @NServiceBus give AI clear patterns Read more in my latest article👇
blog.ecotone.tech/ai-isnt-th…
EcotoneFramework retweeted
You don't need a workflows.
Not for order cancellation timeouts. Not for reminder emails. Probably not even for that multi-step process you're sketching on a whiteboard.
blog.ecotone.tech/three-diff…
EcotoneFramework retweeted
Rewrites have a 23% success rate.
Incremental changes? 4% failure rate.
The math is pretty clear.
blog.ecotone.tech/your-legac…
#php #LegacyCode
EcotoneFramework retweeted
Most vibe-coded apps are architectural time bombs.
But what if the framework guided the AI toward enterprise patterns by default?
So we can build systems that reliable and scalable by default, without the need to even think about it.
blog.ecotone.tech/vibe-codin…
#ai #php #VibeCoding @EcotonePHP
EcotoneFramework retweeted
I've developed #Ecotone Framework based on the principle that we should fully focus on business features, not the technical infrastructure part.
This means that whatever feature we use within Ecotone—Message Deduplication, Dead-Letter, Event Sourcing, etc.—it was always created automatically for us, on demand. And the same flow applies to Message Broker integration - Where we simply define the intent using RabbitMQ, Redis, SQS, etc., and Ecotone takes care of setting up things, including Message Channels creation on the Broker side.
This is great and makes it possible to build systems really quickly, as we can roll out Message Broker integration, Event Streams with reliable patterns like Idempotency, Poison Message Handling, Outbox, etc., without needing to think about any setup. This approach basically lets us build fully reliable systems in just a few lines of code:
👉 github.com/ecotoneframework/…
However, in some cases where optimization of requests is critical, auto-initialization may come with a performance penalty. This may happen, for example, when:
→ Deduplicating messages on the fly (webhooks)
→ Sending messages to the Broker directly from an HTTP Request
In those cases, Auto-Initialization has no chance to cache the status, therefore it will need to check for that resource's existence on each request. To solve those cases, I've now brought Migration support to Ecotone, where we can take over the process of creating those resources, meaning we will now be able to:
✅ View status of all storage resources
✅ Initialize tables/queues during deployment, not at runtime
✅ Generate SQL for integration with Symfony / Laravel migrations
✅ Clean up resources when no longer needed
More information of Ecotone's migration process can be found here:
docs.ecotone.tech/modelling/…
#PHP #Messaging #CQRS #EventSourcing #DDD #SoftwareArchitecture
EcotoneFramework retweeted
To implement an Event-Driven Architecture, we end up following either the "Smart Endpoints, Dumb Pipes" approach or the "Dumb Endpoints, Smart Pipes" approach — either consciously or not.
In my latest article, we dive into what these approaches actually mean, how they are implemented, and which one helps keep systems simple as they grow.
blog.ecotone.tech/implementi…
#php #eda #programming #messaging #events @EcotonePHP
EcotoneFramework retweeted
We don't need to struggle with Message Broker integration, we can actually build production ready asynchronous application with just few lines of code in #PHP.
In latest article "Message Brokers in PHP: From Hundreds of Lines to Just a Few": I am showing the idea behind it:
blog.ecotone.tech/message-br…
#kafka #rabbitmq #messaging #asynchronous #eda @EcotonePHP
EcotoneFramework retweeted
Why does resending work perfectly for #RabbitMQ queues but corrupt #Kafka streams? It's all about channel purpose.
In article "Async Failure Recovery: Queue vs Streaming Channel Strategies", I am diving into Streaming vs Queue Channels, the purpose of those channels, and failure strategies which we can apply based on the scenario we are in.
medium.com/@dariuszgafka/asy…
#DistributedSystems #async #MessageQueues #BackendEngineering #php #development #programming
EcotoneFramework retweeted
Today I'm presenting a new Enterprise feature of Ecotone - "Orchestrator", which allows to build even the most complex Workflows in PHP with ease:
- No complex logic,
- No configuration files
- No External Services
You own and you define your Workflow within PHP:
To define the Workflow, we provide the list of steps you would like to execute, and Orchestrator will take care of connecting the steps together.
This way we can easily build even the most complex workflows, with any customization needed:
- Want to add VIP customer processing? Just inject the step
- Payment taking too long? Simply make it async by adding attribute
- Need parallel operations? Use split mechanism and done
Orchestrators are build on stateless architecture, therefore it eliminates any additional persistence overhead, delivering consistent performance even under high load scenarios.
So you can find out more about Ecotone's Orchestration mechanism, I've wrirtten blog post: blog.ecotone.tech/building-w…
cheers :)
#PHP @EcotonePHP #workflow #webdev #programming
EcotoneFramework retweeted
Zero-config async processing in #PHP?
Add #[Asynchronous("queue")] to any method, to enable asynchronous processing. No configs, extending framework classes, or setting up wiring needed.
@EcotonePHP will automatically:
- Create Message Consumer
- Handle Routing & Serialization
- Manage errors and connection failures
Declare what you want, not how to build it.
This is just a teaser for my recent article on using zero-config for async processing :)
You can find out more here: blog.ecotone.tech/message-ch…
#PHP #AsyncProcessing #DeveloperExperience
EcotoneFramework retweeted
Just published new article.
Let's explore architecture in which scalability and resiliency are side effect of our daily development, not something we struggle for:
dariuszgafka.medium.com/buil…
#web #programming #php #development @EcotonePHP
EcotoneFramework retweeted
Just posted article about practical side of Domain Driven Design:
dariuszgafka.medium.com/350a…
#ddd #development #programming #php
EcotoneFramework retweeted
Just published Article: "Building Workflows in PHP with Ecotone".
Almost any business requires Workflows. Therefore it's important to have ability to keep them maintainable and easy to understand.
dariuszgafka.medium.com/buil…
#php #cqrs #messaging #webdevelopment #programming #development
EcotoneFramework retweeted
Just posted "Integrating PHP Applications with Ecotone and RabbitMQ"
Communication between Applications can be really challenging, yet with right level of abstraction, we can make the process effortless.
dariuszgafka.medium.com/df60…
#programming #php #development #rabbitmq #messaging #ddd











