You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Mark van Renswoude 3ab8b19393 Fixed GitVersion in build 6 days ago
Examples Implemented nullable reference types support 2 months ago
Tapeti Fix and tests for invoking static methods 2 months ago
Tapeti.Autofac Implemented nullable reference types support 2 months ago
Tapeti.Benchmarks Implemented unit tests for QueueArguments attribute 2 months ago
Tapeti.CastleWindsor Implemented nullable reference types support 2 months ago
Tapeti.DataAnnotations Implemented nullable reference types support 2 months ago
Tapeti.Flow Fixed exception in flow requests 2 months ago
Tapeti.Flow.SQL Implemented nullable reference types support 2 months ago
Tapeti.Ninject Implemented nullable reference types support 2 months ago
Tapeti.Serilog Implemented nullable reference types support 2 months ago
Tapeti.SimpleInjector Implemented nullable reference types support 2 months ago
Tapeti.Tests Fix and tests for invoking static methods 2 months ago
Tapeti.Transient Implemented nullable reference types support 2 months ago
build Changed version number strategy to include CommitsSinceVersionSource 3 years ago
docs Added documentation for IFlowParallelRequest 1 year ago
resources Split parts into separate repositories 1 year ago
.gitignore Implemented EasyNetQ Hosepipe compatibility for Tapeti.cmd [ci skip] 3 years ago
GitVersion.yml Preparations for NuGet push 6 years ago
README.md Split parts into separate repositories 1 year ago
Tapeti.png [ci skip] Major refactoring for 2.0 4 years ago
Tapeti.sln Fixed queue arguments error due to wrong value types 2 months ago
Tapeti.sln.DotSettings Fixed queue arguments error due to wrong value types 2 months ago
UNLICENSE Preparations for NuGet push 6 years ago
appveyor.yml Fixed GitVersion in build 6 days ago

README.md

Introduction

Tapeti is a wrapper for the RabbitMQ .NET Client designed for long-running microservices. It’s main goal is to minimize the amount of messaging code required, and instead focus on the higher-level flow.

Key features

  • Consumers are declared using MVC-style controllers and are registered automatically based on annotations
  • Publishing requires only the message class, no transport details such as exchange and routing key
  • Flow extension (stateful request - response handling with support for parallel requests)
  • No inheritance required
  • Graceful recovery in case of connection issues, and in contrast to most libraries not designed for services, during startup as well
  • Extensible using middleware

Show me the code!

Below is a bare minimum message controller from the first example project to get a feel for how messages are handled using Tapeti.

/// <summary>
/// Example of a simple broadcast message used in the standard publish - subscribe pattern
/// </summary>
public class PublishSubscribeMessage
{
    [Required(ErrorMessage = "Don't be impolite, supply a {0}")]
    public string Greeting { get; set; }
}


[MessageController]
[DynamicQueue("tapeti.example.01")]
public class ExampleMessageController
{
    public ExampleMessageController() { }

    public void HandlePublishSubscribeMessage(PublishSubscribeMessage message)
    {
        Console.WriteLine("Received message: " + message.Greeting);
    }
}

More details and examples can be found in the documentation as well as the example projects included with the source.

Documentation

The documentation for Tapeti is available on Read the Docs:

Master branch (stable release)
Documentation Status

Develop branch
Documentation Status

Parts of Tapeti have been split into their own repository. This allows them to have their own version numbers which increases compatibility between shared message packages when services use different Tapeti versions.

Builds

Builds are automatically run using AppVeyor, with the resulting packages being pushed to NuGet.

Master build (stable release) Build status

Latest build Build status