深入实践Spring微服务

需积分: 10 145 浏览量更新于2024-07-18 收藏 19.55MB PDF 举报

"Spring Microservices in Action - John Carnell - Manning" 《Spring Microservices in Action》是一本由John Carnell编著的专业书籍，由Manning出版社发行。这本书详细探讨了如何在Spring框架下构建和管理微服务。Spring Microservices in Action旨在帮助读者理解和实践微服务架构，利用Spring框架的优势来构建可扩展、高可用且松耦合的系统。本书涵盖了微服务的核心概念，包括服务的定义、拆分与设计原则。Spring Boot是实现这一目标的关键工具，它简化了Spring应用的启动和运行过程。书中将深入介绍如何使用Spring Boot创建独立的服务，并配置自动配置功能来减少开发工作量。此外，书中还讨论了服务间的通信方式，如RESTful API设计和使用HTTP/HTTPS进行通信。它可能还会涵盖消息传递系统，如RabbitMQ或Apache Kafka，以实现解耦和异步处理。作者会解释如何使用Spring Cloud Netflix组件，如Eureka（服务发现）、Zuul（边缘服务/API网关）和Hystrix（容错管理）来构建健壮的微服务架构。分布式数据管理和事务处理也是微服务架构中的重要挑战。《Spring Microservices in Action》可能会讲解如何使用Spring Data和Spring Cloud Data Flow来处理数据存储和流处理。同时，书中会讨论数据库选择，如关系型数据库（如MySQL）和NoSQL数据库（如MongoDB），以及如何在微服务之间协调分布式事务。测试和监控对于确保微服务的质量和稳定性至关重要。书中可能包含关于单元测试、集成测试和端到端测试的最佳实践，以及如何使用Spring Boot Actuator和Prometheus等工具进行性能监控和警报设置。最后，书中还会涉及部署和持续集成/持续部署（CI/CD）的话题，比如Docker容器化、Kubernetes和Jenkins的使用，以实现快速、可靠和自动化的服务部署。《Spring Microservices in Action》是一本全面的指南，旨在帮助开发者充分利用Spring框架和微服务架构的力量，构建出高效、灵活且易于维护的现代企业级应用。通过阅读本书，读者可以深入了解微服务的设计理念，掌握实现微服务所需的各种技术，并获得实战经验。

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

Licensed to <null>

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.

Licensed to <null>

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.

Licensed to <null>

剩余385页未读，继续阅读

xiaoxunzi123

粉丝: 1
资源: 9

深入实践Spring微服务

Learn Microservices with Spring Boot

Spring_Microservices_in_Action

Spring Microservices in Action--2017

Spring Microservices in action

Spring.Microservices和 Spring Microservices in Action

Spring Microservices in Action.

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

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 约翰·卡内尔中文版