Client-Server Coupling in gRPC vs REST
Quoting this article – The Other key differences: gRPC vs. REST
section (client server coupling):
C# – Data-Driven Design & Coupling – Mother may I?
I have used data-driven design in the past and it has worked quite well. What I dislike about it is if you need some form of a string whose value has to be updated based on other values.
e.g., “Exports %x percent of %y”. In that case you will need an extra column serving as an identifier, to tell which variable in your class will correspond with the conventional symbols %x and %y. Now, don’t get me wrong, there might be a way around this, but this is not the point of this thread (albeit I would not mind having an answer to this one as well).
Method pattern and method coupling
Disclaimer: I am going to write in Python and in the context of web development with Django, but this question is not language nor framework specific.
An ‘internal’ scope class available only to selected classes
In many languages there is a scope that is just less than public
called internal
.