Shulou(Shulou.com)06/03 Report--

Abstract: this article will discuss how to coordinate the cooperation among the various engineering teams within the company, so as to efficiently maintain the flexibility and flexibility of the system to meet the needs of agile development. This article is selected from Node.js Micro Service.

If a company uses microservices to build software systems, then every stakeholder needs to be involved in decision-making.

Microservice is a major paradigm shift. In general, large organizations tend to build software systems in a fairly traditional way. Each major release takes several months of development cycle, followed by a complete quality assurance phase and a few hours of deployment phase.

When a company chooses to use a micro-service-oriented architecture, the methodology changes completely: each small team is responsible for its own small function points, including their construction, testing, and deployment. Each team does its own job and is able to handle a single task (a micro-service, or rather several micro-services), and each team member will be proficient in the technical and domain knowledge of building software systems.

This is often referred to as a cross-functional team. This is a unit of work made up of a small number of people who have the ability to build high-quality software components.

It is worth noting that team members should have the necessary domain knowledge to understand business requirements.

In my career, most of the main problems that led to the failure of the company were nothing more than the following (from my personal point of view). First of all, there is a view that developers are "brick builders", that is, they can magically understand business flows without communicating in advance. Moreover, there is also the view that if one developer can do X-level work in a week, then 10 developers can deliver 10X-level production in a week. These views are all wrong.

In order to remain efficient and take into account the impact of Conway's Law on the system in changing business processes, members of cross-functional teams that build microservices must be proficient in (not just understand) relevant domain knowledge.

When it comes to the organizational structure of micro-services, autonomy is the key factor. In order to ensure the agility of building micro-services, each team must remain autonomous, which also means ensuring that the technology has its own choice, as shown below:

The language used.

Code specification.

The mode of solving the problem.

The choice of various tools, such as software building, testing, debugging and deployment tools.

This is a very important part because it is the part where we need to define how the company builds the software and may introduce engineering problems.

For example, let's look at the code specification issue, as follows:

Do we need to maintain a uniform code specification across all teams?

Should we let each team have its own code specification?

In general, I prefer the "80% rule": 80% perfection is enough to cover 100% of usage scenarios. This means that relaxing the code specification (which also applies to other areas) and allowing a certain degree of imperfection or personalization can help reduce friction between teams and allow engineers to pay attention to very few important guidelines as soon as possible. such as logging policies and exception handling.

If your code specification is too complex, you will encounter a lot of resistance when one team wants to submit code to other team's micro-services (remember, a team has its own service, but other team members can also contribute to this service).

This article is selected from the Node.js microservice. Click this link to view the book on the blog Viewpoint's website.

For more wonderful articles in time, search for "blog viewpoints" on Wechat or scan the QR code below and follow.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.