GitHub-Mirror/Tapeti
1
0
Fork 0
mirror of synced 2024-06-25 22:07:39 +00:00
Code Issues Projects Releases Wiki Activity
17 Commits 7 Branches 64 Tags 3.3 MiB
C# 99.7%
PowerShell 0.3%
f52ace5f78
Go to file
Mark van Renswoude f52ace5f78 Merge branch 'feature/flow' into develop 
Conflicts:
	Config/IBindingContext.cs
	Config/IConfig.cs
	Config/IMessageContext.cs
	Connection/TapetiConsumer.cs
	Connection/TapetiPublisher.cs
	Connection/TapetiWorker.cs
	Helpers/MiddlewareHelper.cs
	IPublisher.cs
	Tapeti.Flow/Tapeti.Flow.csproj
	Tapeti.Saga/ISagaProvider.cs
	Tapeti.Saga/SagaMiddleware.cs
	Tapeti.Saga/SagaProvider.cs
	TapetiConfig.cs
	Test/MarcoController.cs
	Test/Program.cs
2017-02-07 16:17:35 +01:00
Annotations Started refactoring, not in any usable state yet 2016-12-05 08:00:09 +01:00
Config Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
Connection Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
Default Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
Helpers First working prototype of the flow port 2017-02-05 23:22:34 +01:00
Properties First working prototype of the flow port 2017-02-05 23:22:34 +01:00
Tapeti.Flow Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
Tapeti.SimpleInjector First working prototype of the flow port 2017-02-05 23:22:34 +01:00
Tasks Implemented consumer, serializer, routing key strategy and single-threaded task queue (first working version basically) 2016-11-20 14:34:50 +01:00
Test Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
.gitignore First working prototype of the flow port 2017-02-05 23:22:34 +01:00
ConsumeResponse.cs Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
IConnection.cs Added Saga interfaces 2016-12-07 10:19:16 +01:00
IDependencyResolver.cs First working prototype of the flow port 2017-02-05 23:22:34 +01:00
IExceptionStrategy.cs Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
IExchangeStrategy.cs Work in progress for migrating from Saga to Flow 2017-01-31 12:01:08 +01:00
ILogger.cs Added concept for ILogger 2016-11-21 20:54:29 +01:00
IMessageSerializer.cs Implemented consumer, serializer, routing key strategy and single-threaded task queue (first working version basically) 2016-11-20 14:34:50 +01:00
IPublisher.cs First working prototype of the flow port 2017-02-05 23:22:34 +01:00
IRoutingKeyStrategy.cs Implemented consumer, serializer, routing key strategy and single-threaded task queue (first working version basically) 2016-11-20 14:34:50 +01:00
ISubscriber.cs Back to a working state 2016-12-11 15:08:58 +01:00
MessageController.cs Started refactoring, not in any usable state yet 2016-12-05 08:00:09 +01:00
packages.config Implemented consumer, serializer, routing key strategy and single-threaded task queue (first working version basically) 2016-11-20 14:34:50 +01:00
README.md Started refactoring, not in any usable state yet 2016-12-05 08:00:09 +01:00
Tapeti.csproj Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
Tapeti.sln Work in progress for migrating from Saga to Flow 2017-01-31 12:01:08 +01:00
TapetiConfig.cs Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
TapetiConnection.cs Added request/response validation for non-yieldpoint methods 2017-02-07 16:13:33 +01:00
TapetiConnectionParams.cs First working prototype of the flow port 2017-02-05 23:22:34 +01:00

README.md

Tapeti

'Small to medium-sized and classified as "Least Concern" by the IUCN.'

Wikipedia

Tapeti is a wrapper for the RabbitMQ .NET client designed for long-running microservices with a few specific goals:

  1. Automatic registration of message handlers
  2. Publishing without transport details
  • Routing key generated based on class name
  • One exchange (per service / group of services) to publish them all
  1. Attribute based, no base class requirements (only for convenience)
  2. Graceful handling of connection issues, even at startup
  3. Basic Saga support