Data Processing Pipeline

A code kata to exemplify the use of Onion Architecture structure.

The Problem

You have a system that integrates with 3rd-party systems (through APIs) and from an User perspective he can change data on their system / application and should be updated also on yours. This requires background synchronization to ensure that data is up to date in both systems (assuming that 3rd-party system API allows that). You can easily build services to do that but you want it to be (horizontally) scalable in terms of processing capacity, ensuring the minimal complexity needed in your code base (keep in mind that you can integrate hundreds or even thousands of systems). So, assuming that we have an Onion Architecture structure approach on our application, we should expect "only" to have a new client consumer per new 3rd-party system, that will translate the data into our Domain and then just use our Application layer to import / update data. Because you depend on 3rd-party systems API to sync it might be a good thing to have health and performance monitoring, to allow checking:

• if 3rd-party APIs are up or down;
• if you have problems on any of your data processing pipeline infrastructure components;
• detailed errors that occur while processing data.

The Vision

Provide an easy-to-setup data processing pipeline that addresses the problem, enables horizontal scaling and offers additional tools (web) for integration, healthcheck and performance monitoring, being decoupled from actual dependencies at the same time.

How to contribute?

Please check Up for Grabs and start contributing!

Frameworks / Tools used:

• NancyFx - "...lightweight, low-ceremony, framework for building HTTP based services on .NET and Mono."
• NUnit - unit-testing framework for .NET (to enable integration with Visual Studio, make sure the plugin is installed).
• Moq - mocking framework for .NET.
• NLog - NLog is a free logging platform for .NET
• AutoMoq - an "auto-mocking" container that creates objects for you.
• FluentMigrator - a migration framework for .NET.
• StructureMap - IoC/DI container for .NET.
• NHibernate - open source object-relational mapper for the .NET framework.
• AutoMapper - a convention-based object-object mapper.
• BenchmarkDotNet - .NET library for benchmarking.
• Nancy.Swagger - Nancy Swagger plugin (alternative to Swashbuckle for ASP.NET Web API).