Spring Boot与Spring Cloud：构建企业级微服务实战指南

5星 · 超过95%的资源需积分: 33 163 浏览量更新于2024-07-19 1 收藏 10.84MB PDF 举报

"《Spring Microservices in Action》是一本深入介绍如何使用Java和Spring平台构建微服务应用程序的专业指南。这本书主要针对具有Java和Spring开发经验的开发者，作者John Carnell作为一名资深云工程师，拥有丰富的Java背景，书中详尽讲解了微服务设计的核心原则，以及如何通过Spring Boot简化REST服务的样板代码，Spring Cloud则提供了包括服务发现、路由和部署在内的全套工具。在微服务架构中，本书首先引导读者了解微服务的基本概念，将其代码分解为小型、分布和独立的服务，并强调了设计时的细致规划和架构考虑。作者通过实践案例展示了如何设计并实现微服务，涉及配置管理，如使用Spring Cloud Config管理服务间配置；提升客户端的容错性，通过Spring、Hystrix和Ribbon实现；利用Netflix Zuul实现智能路由；以及部署Spring Cloud应用的策略。书中还探讨了如何在实际场景中应用安全措施，例如服务间的加密通信，以及采用Spring Cloud Stream构建事件驱动架构。另外，通过Spring Cloud Sleuth和Zipkin进行分布式追踪，帮助开发者理解和优化服务之间的调用链路。对于部署微服务，书中的内容将覆盖从本地到企业级环境，再到云端的部署策略。《Spring Microservices in Action》是一本实战性强，理论与实践相结合的书籍，旨在帮助读者掌握在现代软件开发中构建高性能、可扩展的微服务系统的技能。" 这本书不仅适合希望转型或深化微服务技术的开发者，也适合对Spring框架和微服务架构有深入学习需求的专业人士。通过阅读，读者不仅能掌握微服务的设计方法，还能学会如何利用Spring生态系统中的工具来简化开发流程和提升服务质量。同时，购买纸质书的读者还将获赠电子版（PDF、Kindle和ePub格式），方便随时随地学习。"

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 zhailiang UNKNOWN <zhailiang@pinzhi365.com>

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 zhailiang UNKNOWN <zhailiang@pinzhi365.com>

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 zhailiang UNKNOWN <zhailiang@pinzhi365.com>

剩余385页未读，继续阅读

Adventure1995

粉丝: 8
资源: 78

Spring Boot与Spring Cloud：构建企业级微服务实战指南

Spring微服务实战指南：2017版

深入实践Spring微服务

Spring Boot+Vue.js构建后台管理系统源码解析

Spring Microservices in Action.

Spring.5.0.Microservices.2nd.Edition

Spring Microservices epub

Spring_Microservices_in_Action

Spring+Microservices+in+Action

Scala Microservices azw3

spring 5 , Spring Boot 2.0,Spring cloud

最新资源