Spring微服务实战指南：构建高效分布式应用

需积分: 4 124 浏览量更新于2024-07-18 收藏 18.14MB PDF 举报

《Spring Microservices in Action》是一本由John Carnell所著的专业书籍，专为IT专业人士设计，深入探讨了在Java和Spring框架下构建微服务的最佳实践。本书共384页，针对的是第一版，用英语编写，于2017年7月6日由Manning Publications出版。它具有两个独特的ISBN号码：ISBN-10为1617293989，ISBN-13为9781617293986。该书的核心内容围绕Spring框架如何在微服务架构中发挥作用，讲解了如何利用Spring Boot、Spring Cloud等工具来开发、部署和管理分散的微服务组件。作者详细阐述了以下关键知识点： 1. **Spring Boot与微服务**：书中介绍了如何通过Spring Boot简化微服务的初始设置和配置，包括快速启动项目和集成各种依赖。 2. **服务发现与注册**：Spring Cloud中的Eureka或Consul等服务发现工具，如何实现在分布式环境中自动发现和连接服务实例。 3. **API Gateway**：Spring Cloud Gateway作为统一入口，如何提供API版本控制、路由、安全和监控等功能。 4. **模块化和松耦合**：通过Docker和Kubernetes等技术，实现服务的轻量级部署和高可用性。 5. **通信协议**：RESTful API设计和HTTP/2、gRPC等现代协议的应用，以及消息队列如RabbitMQ的整合。 6. **安全性**：讨论了OAuth 2.0、JWT等在微服务间的身份验证和授权策略。 7. **故障处理与容错**：如何设计和实现断路器模式、重试策略和电路恢复，确保服务的健壮性。 8. **监控和日志管理**：介绍如何使用Spring Boot Actuator和ELK Stack等工具进行性能监控和问题追踪。 9. **微服务架构模式**：探索无服务器架构（Serverless）、容器化、事件驱动设计等在微服务实践中的应用。 10. **最佳实践和案例研究**：书中包含实际项目的案例分析，展示了如何将理论知识转化为实践，并分享成功实施微服务的经验教训。《Spring Microservices in Action》不仅提供了技术知识，还强调了架构设计原则和团队协作的重要性。对于希望在Spring框架中深入理解和应用微服务的开发人员来说，这是一本不可或缺的参考书。同时，出版社还提供了折扣订购渠道，并鼓励读者通过Manning Publications的网站或邮件联系获取更多信息。版权方面，未经许可，不得复制或传播此书的任何部分。

preface

It’s ironic that in writing a book, the last part of the book you write is often the begin-

ning of the book. It’s also often the most difficult part to put down on paper. Why?

Because you have to explain to everyone why you’re so passionate about a subject that

you spent the last one and a half years of your life writing a book about it. It’s hard to

articulate why anyone would spend such a large amount of time on a technical book.

One rarely writes software books for the money or the fame.

Here’s the reason why I wrote this book: I love writing code. It’s a calling for me

and it’s also a creative activity—akin to drawing, painting, or playing an instrument.

Those outside the field of software development have a hard time understanding this.

I especially like building distributed applications. For me, it’s an amazing thing to see

an application work across dozens (even hundreds) of servers. It’s like watching an

orchestra playing a piece of music. While the final product of an orchestra is beauti-

ful, the making of it is often a lot of hard work and requires a significant amount of

practice. The same goes for writing a massively distributed application.

Since I entered the software development field 25 years ago, I’ve watched the

industry struggle with the “right” way to build distributed applications. I’ve seen dis-

tributed service standards such as

CORBA rise and fall. Monstrously big companies

have tried to push big and, often, proprietary protocols. Anyone remember Micro-

soft’s Distributed Component Object Model

(DCOM) or Oracle’s J2EE’s Enterprise

Java Beans

2 (EJB)? I watched as technology companies and their followers rushed to

build service-oriented architectures

(SOA) using heavy XML-based schemas.

In each case, these approaches for building distributed systems often collapsed

under their own weight. I’m not saying that these technologies weren’t used to build

some very powerful applications. The reality is that they couldn’t keep up with the

PREFACExvi

demand of the users. Ten years ago, smartphones were just being introduced to the

market and cloud computing was in the earliest stage of infancy. Also, the standards

and technology for distributed application development were too complicated for the

average developer to understand and easily use in practice. Nothing speaks truth in

the software development industry like written code. When the standards get in the

way of this, the standards quickly get discarded.

When I first heard of the microservices approach to building applications I was

more than a little skeptical. “Great, another silver-bullet approach to building distrib-

uted applications,” I thought. However, as I started diving into the concepts, I realized

the simplicity of microservices could be a game changer. A microservice architecture

focuses on building small services that use simple protocols (

HTTP and JSON) to com-

municate. That’s it. You can write a microservice with nearly any programming lan-

guage. There’s beauty in this simplicity.

However, while building an individual microservice is easy, operationalizing and

scaling it is difficult. Getting hundreds of small distributed components to work

together and then building a resilient application from them can be incredibly diffi-

cult to do. In distributed computing, failure is a fact of life and how your application

deals with it is incredibly difficult to get right. To paraphrase my colleagues Chris

Miller and Shawn Hagwood: “If it’s not breaking once in a while, you’re not building.”

It’s these failures that inspired me to write this book. I hate to build things from

scratch when I don’t have to. The reality is that Java is the lingua franca for most appli-

cation development efforts, especially in the enterprise. The Spring framework has for

many organizations become the de facto framework for most application develop-

ment. I’d already been doing application development in Java for almost 20 years (I

remember the Dancing Duke applet) and Spring for almost 10 years. As I began my

microservices journey, I was delighted and excited to watch the emergence of Spring

Cloud.

The Spring Cloud framework provides out-of-the-box solutions for many of the

common development and operational problems you’ll run into as a microservice

developer. Spring Cloud lets you use only the pieces you need and minimizes the

amount of work you need to do to build and deploy production-ready Java micro-

services. It does this by using other battle-hardened technologies from companies and

groups such as Netflix, HashiCorp, and the Apache foundation.

I’ve always considered myself an average developer who, at the end of the day, has

deadlines to meet. That’s why I undertook the project of writing this book. I wanted a

book that I could use in my day-to-day work. I wanted something with direct (and

hopefully) straightforward code examples. I always want to make sure that the mate-

rial in this book can be consumed as individual chapters or in its entirety. I hope you

find this book useful and I hope you enjoy reading it as much as I enjoyed writing it.

ACKNOWLEDGMENTSxviii

challenged me to become a better author. I’d also like to thank Raphael Villela and

Joshua White, my technical editors, who constantly checked my work and ensured the

overall quality of the examples and the code I produced. I’m extremely grateful for

the time, talent, and commitment each of these individuals put into into the overall

project. I’d also like to thank the reviewers who provided feedback on the manuscript

throughout the writing and development process: Aditya Kumar, Adrian M. Rossi,

Ashwin Raj, Christian Bach, Edgar Knapp, Jared Duncan, Jiri Pik, John Guthrie, Mirko

Bernardoni, Paul Balogh, Pierluigi Riti, Raju Myadam, Rambabu Posa, Sergey Evsikov,

and Vipul Gupta.

I want to close these acknowledgments with a deep sense of thanks for the love and

time my family has given me in working on this project. To my wife Janet, you have

been my best friend and the love of my life. When I’m tired and want to give up, I only

have to listen for the sound of your footsteps next to me to know that you’re always

running beside me, never telling me no, and always pushing me forward.

To my son Christopher, you’re growing up to be an incredible young man. I can-

not wait for the day when you truly discover your passion, because there will be noth-

ing in this world that can stop you from reaching your goals.

To my daughter Agatha, I’d give all the money I have to see the world through

your eyes for just 10 minutes. The experience would make me a better author and

more importantly a better person. Your intellect, your power of observation, and cre-

ativity humble me.

To my four-year-old son, Jack: Buddy, thank you being patient with me whenever I

said, “I can’t play right now because Daddy has to work on the book.” You always make

me laugh and you make this whole family complete. Nothing makes me happier than

when I see you being the jokester and playing with everyone in the family.

My race with this book is done. Like my marathon, I’ve left nothing on the table in

writing this book. I have nothing but gratitude for the Manning team and the

MEAP

readers who bought this book early and gave me so much valuable feedback. I hope in

the end that you enjoy this book as much as I enjoyed writing it. Thank you.

剩余385页未读，继续阅读

chenlei002

粉丝: 0
资源: 5

Spring微服务实战指南：构建高效分布式应用

Spring Microservices in action

Spring.Microservices和 Spring Microservices in Action

Spring Microservices in Action.

Spring Microservices in Action--2017

Spring Microservices in Action 约翰·卡内尔 中文版

Spring Microservices in Action 第二版代码示例.zip

spring-microservices-in-action:《 Spring Microservices in Action（John Carnell）》一书的源代码，以及有关Spring Boot for Microservices的技术要点的个人摘要-redis source code

《Spring Microservices in Action》(Manning 2017)英文原版

Spring Microservices in Action-Manning(2017)【E文】

spring microservices in action 电子书

最新资源

Spring Microservices in Action 约翰·卡内尔中文版