3 years ago

SOLID is big part of working at Cobiro. It allows us to write scalable and easy to maintain code, when combining it with Test Driven Development and Continuous Deployment, we are able to ship to production multiple times a day and give new features into hands of users faster.

SOLID is especially important when you work in a startup or a scale-up, because it allows you to modify your code when the business requirements change (and they change constantly in a reality when you want to build the next unicorn startup!).

I would advise to keep it simple and generic (it is infrastructure layer after all) so try to use parameters and generic methods because changing implementation of this interface in another means of transport will be easier.

This ended up in an anaemic domain model and almost empty Service classes that were one of two following anti patterns: Even though I have touched upon Domain Driven Design and Aggregates, what you should understand from this article is that you should define a smaller well defined interfaces that allow you to switch implementation of your classes.