Patterns for Building and Deploying Microservices

本文探讨了微服务架构带来的操作复杂性及管理方法。通过分解大型应用为小型服务,并采用自动化部署与基础设施自动化等手段来简化流程。文章强调了业务与架构的一致性,以及单一职责原则的重要性。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

Managing microservices means looking afterlots of small systems talking to each other and automated provisioning as wellas infrastructure automation is crucial, James Lewis states when sharingtechniques and practices that have helped him manage the increased operationalcomplexity a microservice architecture gives.

James, a consultant working for ThoughtWorks,describes the origin of microservices as a reaction to how we have beenbuilding big monolithic applications that are difficult to change, test andmanage; essentially big balls of mud with tangled spaghetti code. The solutionbeing building smaller things and make them communicate in some way.

For James microservices means taking a largeapplication, identifying the bounded contexts and business capabilities withinand splitting them out, crucially taking data with them, i.e. applicationdatabases instead of one integration database. The key thing is starting at thetop with a context map in order to understand the business domain and Jamesrefers to his colleague Ian Cartwright:

There should be business and architecture isomorphism. A business person should be able to look at a high level map of the architecture and see the business represented there and similarly as technologists we should be able to look at the business and see the architecture represented there.

Animportant aspect of microservices is size and James sees Single ResponsibilityPattern (SRP) as a good measure. A service should have a single reason tochange which in practice means it should be small and focused enough to bepossible to grasp conceptually.

Acore concept of microservices for James is the possibility to independentlydeploy and scale each service; a service may be deployed as several instancesand different services may be hosted on the same server. When building anddeploying distributed systems, a focus on automated provisioning is crucialJames emphasizes, each service or application have to be built, deployed andscaled automatically. With microservices a lot of the complexity comes fromintegration but we can apply patterns to solve this and refers to the bookContinuous Delivery for patterns of build pipelines.

Infrastructureautomation with tools like Chef and Puppet helping in automatic provisioning ofmachines is central in managing the complexity coming with lots of services.Phoenix infrastructure patterns describe how we by using infrastructureautomation always should be able to recreate all infrastructure, e.g. we shouldbe able to wipe a box and run a script to rebuild it complete with alldependencies.

Related Topics:

1.Microservice

http://martinfowler.com/articles/microservices.html

2.Step by step to build microservice

http://www.simplicityitself.com/courses/1-day-tutorial-introduction-to-building-microservices/

3.Microservice and SOA

http://www.infoq.com/news/2014/03/microservices-soa/

manning.microservices.patterns是指微服务架构模式方面的内容。微服务是一种架构风格,它将一个应用程序拆分为一组小的、独立的服务,每个服务都可以独立部署、扩展和维护。manning.microservices.patterns通过提供一些常见的模式,帮助开发人员构建可靠、可伸缩、可维护的微服务架构。 首先,manning.microservices.patterns介绍了服务拆分的模式。它提供了一些指导原则,帮助开发人员确定应该将哪些功能拆分为独立的服务,以及如何定义服务边界。这样可以确保每个服务都专注于一个明确的业务领域,并且可以独立地开发和部署。 其次,manning.microservices.patterns讨论了服务间通信的模式。微服务架构中,各个服务需要相互通信来实现业务流程。这本书介绍了一些常见的通信模式,例如同步调用、异步消息传递和事件驱动架构。开发人员可以根据实际需求选择适合的通信方式。 此外,manning.microservices.patterns还介绍了服务发现和负载均衡的模式。由于微服务架构中的服务数量庞大,需要有一种方法来发现和跟踪可用的服务实例。这本书提供了一些模式,如服务注册与发现、负载均衡和断路器模式,帮助开发人员实现可靠的服务发现和负载均衡机制。 最后,manning.microservices.patterns还探讨了监控和故障处理的模式。微服务架构中,每个服务都可以独立部署和维护,因此需要一种方法来监控服务的健康状况,并及时处理故障。这本书介绍了一些常见的监控和故障处理模式,例如服务指标监控、日志聚合和异常处理模式。 总之,manning.microservices.patterns是一本关于微服务架构模式的书籍,它提供了一些常见的模式,帮助开发人员构建可靠、可伸缩、可维护的微服务架构。这些模式涵盖了服务拆分、服务间通信、服务发现和负载均衡、监控和故障处理等方面,可以帮助开发人员在构建微服务架构时更加高效地解决各种技术挑战。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值