How can you establish and enforce microservices conventions?

由人工智能和领英社区提供技术支持

Microservices architecture is a popular way to design and develop software applications that are composed of independent and loosely coupled services. Each service has its own responsibility, functionality, and data, and communicates with other services through well-defined interfaces. However, to ensure consistency, maintainability, and scalability of your microservices, you need to establish and enforce some conventions across your services. In this article, you will learn how to do that using some practical tips and tools.

在这篇协作文章中查找专家回答

由社区从 7 条内容中精选。了解更多

1 Define your domain boundaries

One of the first steps to establish microservices conventions is to define your domain boundaries. This means identifying the core business domains and subdomains of your application, and mapping them to the services that implement them. A common approach to do this is to use domain-driven design (DDD), which helps you to model your domain based on the language, concepts, and rules of your business stakeholders. By defining your domain boundaries, you can ensure that your services are aligned with your business needs, and that they have clear and cohesive responsibilities.

添加您的观点

Prabhat Kumar

Sr. DevSecOps @ Terrascope
举报内容
Once upon a tech odyssey, I ventured into DevOps. The first lesson: unite devs and ops for seamless collaboration. Automation became my ally, liberating time and boosting efficiency. Scaling the CI/CD mountain taught resilience and rapid, reliable code delivery. Monitoring and feedback loops were vital, steering growth through constant adaptation. Security, an essential voyage across the seas of DevSecOps, was a must. Alongside fellow explorers, we shared victories and knowledge. The journey never truly ends; it's an ongoing cycle of learning and adapting. With newfound wisdom, I eagerly await the next chapter in this ever-evolving world of DevOps.

已翻译

赞
Denis Baltor

"Enterprises can learn not only how to get faster, but go fast forever."
举报内容
The best way to make teams, and hence their microservices, really autonomous is to align them “to a flow of work from (usually) a segment of the business domain” which Matthew Skelton and Manuel Pais have called Stream-aligned teams in their best-seller Team Topologies. High-performance teams share two essential characteristics: 1) Product strategy autonomy which enables them to conduct user research and experiments on an ongoing basis. 2) Architectural autonomy which enables them to make design decisions with no or minimal coordination with other teams. Software engineers also need to reach out to the Domain Experts to understand what business invariants are supposed to be enforced before defining the right size for microservices.

已翻译

赞

2 Design your service contracts

Another important step to establish microservices conventions is to design your service contracts. These are the specifications that define how your services expose their functionality and data to other services and clients. They include the service endpoints, the request and response formats, the error handling, and the security mechanisms. A common approach to design your service contracts is to use a standard format such as OpenAPI, which allows you to document and validate your service interfaces using a human-readable and machine-processable language. By designing your service contracts, you can ensure that your services are interoperable, reliable, and secure.

添加您的观点

Prabhat Kumar

Sr. DevSecOps @ Terrascope
举报内容
Designing clear service contracts is a pivotal step in microservices architecture. Service contracts outline how services interact, specifying endpoints, data formats, error handling, and security. Using standardized formats like OpenAPI ensures clarity and validation. Well-crafted contracts promote interoperability, reliability, and security, forming the foundation of a robust microservices system.

已翻译

赞
Denis Baltor

"Enterprises can learn not only how to get faster, but go fast forever."
举报内容
When we have got a number of decentralised teams and everything is distributed — applications, services and even integration — we better have clear contracts between all involved parts, in other words, we need in place a solid API-First strategy. This means APIs, both synchronous (e.g. REST, gRPC) and asynchronous (messaging), being treated as first-class citizens. But working with traditional API gateways curated by centralised teams is not a viable option for organisations practising DevOps. To solve this issue, Distributed API Management delegates and distribute API assets (APIs, users, and content) to the teams responsible for them and uses automated contract-testing to avoid breaking changes going unnoticed.

已翻译

赞

3 Implement your coding standards

A third step to establish microservices conventions is to implement your coding standards. These are the rules and guidelines that define how you write, format, and organize your code within and across your services. They include the naming conventions, the indentation, the comments, the code quality, and the testing practices. A common approach to implement your coding standards is to use a code formatter such as Prettier, which automatically formats your code according to a predefined configuration. You can also use a code linter such as ESLint, which checks your code for syntax errors, bugs, and style issues. By implementing your coding standards, you can ensure that your code is readable, maintainable, and consistent.

添加您的观点

Prabhat Kumar

Sr. DevSecOps @ Terrascope
举报内容
Establishing coding standards in microservices is crucial. These standards define how code is written, formatted, and organized. They cover naming conventions, indentation, comments, code quality, and testing practices. Tools like Prettier for formatting and ESLint for checking syntax and style help enforce these standards, promoting readable, maintainable, and consistent code across services. Adhering to coding standards enhances collaboration and reduces development complexities.

已翻译

赞

4 Enforce your architectural constraints

A fourth step to establish microservices conventions is to enforce your architectural constraints. These are the rules and policies that define how you structure, deploy, and monitor your services within your application. They include the service dependencies, the communication patterns, the deployment environments, and the observability tools. A common approach to enforce your architectural constraints is to use a service mesh such as Istio, which provides a uniform layer of infrastructure that manages the network traffic, security, and observability of your services. You can also use a configuration management tool such as Ansible, which automates the provisioning, deployment, and orchestration of your services. By enforcing your architectural constraints, you can ensure that your services are scalable, resilient, and performant.

添加您的观点

Prabhat Kumar

Sr. DevSecOps @ Terrascope
举报内容
Enforcing architectural constraints is vital in establishing microservices conventions. These rules govern structure, deployment, and monitoring, encompassing service dependencies, communication patterns, deployment environments, and observability tools. Tools like Istio (a service mesh) or Ansible (for automation) help enforce these rules, ensuring scalability, resilience, and performance in your microservices ecosystem. Stay compliant to prosper in the world of microservices.

已翻译

赞

5 Review your service evolution

A fifth step to establish microservices conventions is to review your service evolution. This means evaluating and updating your services based on the feedback, requirements, and changes of your business and technical environment. You need to consider how your services can adapt to new features, bug fixes, performance improvements, and security enhancements. A common approach to review your service evolution is to use a versioning strategy such as semantic versioning, which assigns a unique identifier to each service release based on the type and impact of the changes. You can also use a change management tool such as Git, which tracks and records the history and progress of your service development. By reviewing your service evolution, you can ensure that your services are relevant, up-to-date, and compatible.

添加您的观点

Prabhat Kumar

Sr. DevSecOps @ Terrascope
举报内容
Reviewing service evolution is crucial in establishing microservices conventions. It involves assessing and updating services based on feedback, business needs, and tech changes. Adaptability to new features, bug fixes, and security enhancements is vital. Semantic versioning and tools like Git aid in tracking and managing changes. Regular review ensures services stay relevant and compatible with evolving requirements. Stay agile and responsive to maintain a robust microservices architecture.

已翻译

赞

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Software Design

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How can you establish and enforce microservices conventions?

1

2

3

4

5

6

1 Define your domain boundaries

2 Design your service contracts

3 Implement your coding standards

4 Enforce your architectural constraints

5 Review your service evolution

6 Here’s what else to consider

Software Design

给文章评分

感谢您的反馈

更多Software Design相关文章

更多相关阅读内容

How can you establish and enforce microservices conventions?

1

2

3

4

5

6

1 Define your domain boundaries

2 Design your service contracts

3 Implement your coding standards

4 Enforce your architectural constraints

5 Review your service evolution

6 Here’s what else to consider

Software Design

给文章评分

感谢您的反馈

查看其他技能