We had a team discussion today about applying SOLID principles to Service Oriented Architecture. Intuitively it felt like these principles apply even more so across services, but we wanted to hear counter arguments. Which cases have you seen this fall apart?
Ask HN: How should we think about SOLID principles in SOA?
1–3 of 3 posts
Re: Ask HN: How should we think about SOLID principles in SOA?
#2^ Context: Most reading SOLID use lower level code examples, but one could imagine that relatively large network/serialization overhead compared to simple method/function calls could conceivably change the rules in certain scenarios. Wondered if people had good examples to share.
Re: Ask HN: How should we think about SOLID principles in SOA?
#3SOLID is going to be problematic and it’s easier to focus on baser things like cohesion and writing simple, unabstracted code.
https://solid-is-not-solid.com has a snarky take on this but I wrote it to be apt as well.