Stepankha Yuliannia wrote:Hi Alexander,
Looking at the limited preview, I already like the book :-)
Thank you!
Stepankha Yuliannia wrote:Hi Alexander,
It seems to cover functional architectural design patterns and explores the functional design by looking at object-oriented principles and learn how they can be reapplied to a functional environment - which is exactly for me.
Yeah, you're right. I'm paying a lot of attention to building bridges between old good OOP software design and FP software design. I can't say the latter is "old good", or "old" even considering that FP was here for 60 years. But I personally don't think we have a complete story of Software Design for FP, in particular how the known OO principles are applicable to FP. My thesis is that they are very applicable and very needed.
Stepankha Yuliannia wrote:Hi Alexander,
My question to you is what are your views on when do we need a service-oriented approach (and therefore a service-oriented architecture) and when is better to avoid it?
This is a good question, and I don't think we can find a definite answer that works for all. My personal view is that its existence has some reasons that we can't deny, and my wish will be that those services be designed well because if not, it's very hard to maintain. I'm not a fan of SOA, and most of my projects were like monolith REST applications which in turn could be separated externally. I mean, if you have a rich HTTP API described in a single code base, you can separate it on the level higher and make different instances of it to expose different parts of the API. This is not exactly SOA, but still has some of its properties.
So I believe people need SOA, and use it for reasons, and they are paying all the bills. As long as this architecture survives, I guess there are good applications of it.