官术网_书友最值得收藏!

Scaling and deployment

Finally, having your application split into components makes it easier to scale depending on your constraints. Let's say you start getting a lot of customers who book hotels daily, and the PDF generation starts to heat up the CPUs. You can deploy that specific microservice in some servers that have bigger CPUs.

Another typical example are RAM-consuming microservices like the ones that interact with memory databases like Redis or Memcache. You could tweak your deployments, consequently, by deploying them on servers with less CPU and a lot more RAM.

We can, thus, summarize the benefits of microservices as follows:

  • A team can develop each microservice independently, and use whatever technological stack makes sense. They can define a custom release cycle. All they need to define is a language-agnostic HTTP API.
  • Developers break the application complexity into logical components. Each microservice focuses on doing one thing well.
  • Since microservices are standalone applications, there's a finer control on deployments, which makes scaling easier.

The microservices architecture is good at solving a lot of the problems that may arise once your application starts to grow. However, we need to be aware of some of the new issues they also bring in practice.

主站蜘蛛池模板: 佛冈县| 宁强县| 合水县| 乐清市| 唐海县| 镇巴县| 南通市| 淳化县| 宁远县| 阿克| 钦州市| 锡林郭勒盟| 东光县| 鄂托克旗| 无棣县| 环江| 临安市| 周宁县| 平塘县| 古交市| 大埔县| 定日县| 佛教| 和顺县| 潍坊市| 贺州市| 陆丰市| 钟祥市| 通化县| 阳信县| 五寨县| 抚顺市| 囊谦县| 砚山县| 玉溪市| 沁阳市| 平陆县| 若尔盖县| 东安县| 金湖县| 小金县|