Replacing a legacy .Net monolith with a .Net monolith Rest API 🤦‍♂️

  • 2
    Welcome to the macro-service... best to build it using microservices, tight coupling, and and no gateway. Tests should be forced to all run together. Only write unit tests (because functional/integration tests are slow and therefore, useless). And they should all compile together into one api. Nancy everywhere!

    All so you can claim TDD microsercices and not be lying.

    At least that’s how we were doing it.
Add Comment