Early in my career as a software engineer I got a very good advice from a hand full of well-known veterans in the software industry.

I asked them the following question: “How can I become a software engineer / architect as you are?”

I’m a Solution Architect, a Cloud Solution Architect - to be complete - a Microsoft Cloud Solution Architect for Azure Applications Development.

I’m developing solution architectures each week, with my customers, using Azure services, existing systems, partner offerings and common sense.

And unfortunately, in the past I’ve noticed more and more often that “Cloud Solution Architecture” stops before the level of implementation details.

As you already know, since April 6, 2017 Azure Functions has direct integration with Application Insights.

One of the already know issues is that dependencies that the function has to other services don’t show up automatically.

But with some manual work, it’s possible today!

A long time ago I already had a blog but then I decided to focus on twitter and internal community stuff.

The world keeps turning and I notice more and more often, how the same questions come up with my different customers or in community conversations.

Thus I decided to start a new blog and focus on lessons learned, best practices and guidelines at my day to day job as a Cloud Solution Architect spezialized at Azure Application Development.

协议是什么，简单来说：协议是两个实体之间正确交流信息的规则。而实体这个词语的含义非常广泛，它可以是我们传统意义上的网络通信节点，网络应用程序，还可以是两个进程，甚至还可以是两个线程。只要两个可以划分的独立体需要出现信息，那么它们之间都存在着协议。唯一的差别就是协议的传输方式和复杂度。只要有交流，就会有协议！