Skip to content

POC for .NET Core domain service using Kafka as a message broker

Notifications You must be signed in to change notification settings

JonathanEbel/Kafka-Domain-Service

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

27 Commits
 
 
 
 
 
 

Repository files navigation

Kafka-Domain-Service

POC for .NET Core domain service using Kafka as a message broker

To develop for this locally:

  • Install the latest version of .NET 2.2 from http://dot.net
  • You can now compile everything: Navigate to the root directory and type dotnet build
  • (That's really it...)

To run this locally there are dependencies on:

  • Kafka
  • Zookeeper
  • PostgreSQL

I have created a docker-compose.yml in the root directory which will set up and run all of those dependencies for you. In the same docker-compose there is also a pgadmin image which will give you SQL management tools locally over port 80 to administer PostgreSQL.

Run all of your data migrations:

  • simply run ./update-databases in the root directory
  • (Postgres needs to be running either in a container or installed locally for the migrations to be applied. You will know if it doesn't work)

Each project with a .Service suffix is an API project for a particuar domain and each project with a .Worker suffix is a command and event consumer application.

  • Each one of these Services or Workers can be started by navigating to their corresponding directory and typing dotnet run. (Workers need ro have this command followed by a single argument that tells that app what environment they are runinng as. For example: Locally we use: dotnet run Development

Running this on other environments

...instructions coming soon

About

POC for .NET Core domain service using Kafka as a message broker

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages