Choosing Between Layered Architecture and Vertical Slices in Effect for a Monolith Project
I am pondering whether to choose a layered architecture or vertical slices for a smallish-medium scale monolith project, and one of the things that I am trying to assess is the pain of creating multiple services in each slice.
How much of a pain or a blessing do you think creating and composing layers in Effect is when you have lots of them? I really like to organise my codebase by feature but it also comes at the cost of repetition and declaring layers is kind of boilerplaty. However I can see a benefit in having a structured way of dealing with dependencies because enforcing a standard structure in this kind of setup can be challenging since each package is independent and can do its own thing.
I'm really looking for general feelings, opinions and personal preferences here as I don't think there is a right or wrong answer at this scale.
How much of a pain or a blessing do you think creating and composing layers in Effect is when you have lots of them? I really like to organise my codebase by feature but it also comes at the cost of repetition and declaring layers is kind of boilerplaty. However I can see a benefit in having a structured way of dealing with dependencies because enforcing a standard structure in this kind of setup can be challenging since each package is independent and can do its own thing.
I'm really looking for general feelings, opinions and personal preferences here as I don't think there is a right or wrong answer at this scale.
Similar Threads
Was this page helpful?
