文件名称：Microservices and Containers-Addison-Wesley(2018).epub
文件大小：19.71MB
文件格式：EPUB
更新时间：2021-04-14 15:30:46
微服务 容器
As always, the technology sector is in the midst of momentous transitions—the Internet of things, software-enabled networking, and software as a service (SaaS), to name but a few. Because of these innovations, there is a large demand for platforms and architectures that can improve the process of application development and deployment. Companies of many sizes now require frameworks and architectures that can simplify their applications’ update processes, allowing their latest versions to go to market more frequently without adding undue overhead to the development and deployment teams. This transition, like many of its cousins, is still young, yet many technologies and frameworks in the space have already come and gone. The winners remain standing, however, continuing to improve the world’s software by allowing its developers—us—to create new applications and update existing ones with more agility than ever before. Two such winners? Microservices and containers, red-hot topics that, in my opinion, also possess staying power. Compared to the monolithic approach, the most common way of developing and deploying applications, microservices simplify those processes, especially with large projects that require multiple teams and increasingly long code. In such cases, even a small change in the code can cause serious delays. Microservices can handle today’s large codes by incorporating agility and scalability into application development and deployment, all within a proven paradigm. That’s where this book comes in. When I first started learning about microservices, there were several valuable online resources (in particular, I recommend the websites microservices.io, by Chris Richardson, and martinfowler.com, by James Lewis and Martin Fowler), but I could not find many books that systematically built a case for why a CTO or director of an engineering team should (or should not) make the transition to microservices. There was a clear gap in the market; the more I mastered the subject matter, the more I thought, “Why can’t I be the one to fill that gap?” Soon I was brainstorming ideas for a book of my own.