Good Dev & Design Service: What are the common bad practices in developing a communication level?

Question

I am currently studying best practices (at a fairly high level) for developing applications for systems with a high degree of support that lead to a minimal change in friction. By “communication layer” I mean web services, service buses, and common network transmission technologies.

From your experience, what do you consider common mistakes and bad practices when it comes to developing a communication level, and what measures have you taken / put in place / or can you recommend making the communication level better from the developer's point of view?

An example response may include: What are the most common causes of weakly scalable and expandable communication levels? + What measures can be taken (whether during design or refactoring) to cure this problem?

I am looking here for war stories and some real-world recommendations that I can build in publicly available instructions and samples.

Answer 1

The problem in the question itself is the "level of communication."

Communication should not be a level in itself, at best you can think of it as a layer. It does not have to be physically separate.

Hope this helps.