Skip to content

Commit 098f227

Browse files
author
Sharifuzzaman Nakib
committed
Some adjustments
1 parent 910ae2f commit 098f227

2 files changed

Lines changed: 5 additions & 1 deletion

File tree

documentation/docs/concepts/generic-broker.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,10 @@ Most brokers also allow you to configure **routing** between Publish Endpoints a
2020
This means that when a message arrives at a Publish Endpoint, the broker forwards it to one or more Receive Endpoints based on the defined routing configuration.
2121
(You can still send messages directly to the ReceiveEndpoint if needed.)
2222

23-
These behaviors are consistent across brokers.
23+
These behaviors are consistent across brokers.
2424

25+
Some databases, such as SQL Server or PostgreSQL, provide features that allow them to function as a simple message broker in certain workloads.
26+
In OpenTransit, SQL Server and PostgreSQL can also be used as Brokers, leveraging these shared capabilities.
2527

2628

2729
## The Generic Broker Concept

documentation/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ Hey there! 👋
1010
**OpenTransit** is a free and open-source alternative to the most popular messaging framework in .NET — **[MassTransit](https://github.com/MassTransit/MassTransit)**. It is a **community-maintained fork of MassTransit v8**, the last open-source version before it went commercial.
1111
We started this project because we believe great tools should stay open and accessible to everyone.
1212

13+
We’re building OpenTransit to become the de-facto standard for distributed messaging — the natural first choice in a developer’s mind whenever reliability and scale enter the conversation.
14+
1315
However, there is a catch: OpenTransit will be supported only for **.NET 10+**.
1416

1517
---

0 commit comments

Comments
 (0)