https://github.com/tpierrain/outside-in-hexagonal

A greenfield code kata to show how to build a system following the outside-in TDD approach and relying on the hexagonal architecture
https://github.com/tpierrain/outside-in-hexagonal

Last synced: about 5 hours ago
JSON representation

A greenfield code kata to show how to build a system following the outside-in TDD approach and relying on the hexagonal architecture

• Host: GitHub
• URL: https://github.com/tpierrain/outside-in-hexagonal
• Owner: tpierrain
• Created: 2015-05-27T05:38:53.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2015-05-27T05:50:28.000Z (over 9 years ago)
• Last Synced: 2023-04-03T14:07:24.373Z (over 1 year ago)
• Language: C#
• Size: 594 KB
• Stars: 3
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: Readme.md

Awesome Lists containing this project

README

        
Outside-in hexagonal this!

============================

__A code kata by [@tpierrain](https://twitter.com/tpierrain)__

## Objective

Implement a *"service"* that is able to provide *Pasta Recipes* following the __outside-in TDD approach__ and the __hexagonal architecture__ to prevent domain code from being impacted by infrastructure code.

## Details

 1. The *"service"* should allow its consumers:

  - to get the *Recipe* (i.e. the list of the ingredients) of a *Pasta* given its name

  - to get the list of all the *Pastas* that have a given *Ingredient*

  - to add the *Recipe* of a new *Pasta* and to persist it

 2. A *Pasta Recipe* is a list of ingredient associated with the name of a *Pasta*. E.g.:

  - gnocchi(eggs-potatoes-flour)

  - spaghetti(eggs-flour)

  - organic spaghetti(organic eggs-flour)

  - spinach farfalle(eggs-flour-spinach)

  - tagliatelle(eggs-flour)

 3. __The domain model should not be the same as the one for the communication__ with the service consumers (i.e. the DTOs).