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? | Better HN
^ 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.