Advice on Patterns and Practices for Functional Programming with Effect in a RESTful API Context
I'm new to effect and maybe even to functional programming need some advice on patterns & practices
I've been doing OOO for so long and used some funcitonal programing along the way, but the most important aspect are patterns and practices for a sucessful implementation. I love separation of concerns and code readibility, help me organized everything I do. Been using the library for 4 weeks now. I understand the library, but jumped into an already existing code base (a Restful API) and I'm sooo confused. I'm seeing effects calling effects calling effects..so basically concerns feel completely coupled. Return Types are so complext that they are hard to track down causing TS gymnastics and I need to code some unit test. The nesting starting to feel like side effects. Does functional programming share patterns and practices when building complete solutions as other paradigms? if not what P&P should this solutions should follow. some of the P&P that I use when building an API are like
- Routing Layer,
- Controllers for single service being called and sagas when services intreact with each other services ,
- Service Layer. In this layer services never call other services.. External APIs are not treated like services but proxies like calling a simple function.
- Repo Layer
Thank you.
I've been doing OOO for so long and used some funcitonal programing along the way, but the most important aspect are patterns and practices for a sucessful implementation. I love separation of concerns and code readibility, help me organized everything I do. Been using the library for 4 weeks now. I understand the library, but jumped into an already existing code base (a Restful API) and I'm sooo confused. I'm seeing effects calling effects calling effects..so basically concerns feel completely coupled. Return Types are so complext that they are hard to track down causing TS gymnastics and I need to code some unit test. The nesting starting to feel like side effects. Does functional programming share patterns and practices when building complete solutions as other paradigms? if not what P&P should this solutions should follow. some of the P&P that I use when building an API are like
- Routing Layer,
- Controllers for single service being called and sagas when services intreact with each other services ,
- Service Layer. In this layer services never call other services.. External APIs are not treated like services but proxies like calling a simple function.
- Repo Layer
Thank you.
Similar Threads
Was this page helpful?
