Spring微服务实战

需积分: 8 179 浏览量更新于2024-07-18 收藏 19.65MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"Spring Microservices in Action by John Carnell - A True PDF edition published in 2017." 《Spring Microservices in Action》是John Carnell撰写的一本深入探讨Spring框架下微服务开发的专业书籍，旨在帮助读者掌握如何在实际项目中有效地运用Spring构建微服务架构。该书于2017年由Manning Publications发行。微服务架构是一种将单一应用程序分解为一组小型、独立的服务的软件设计模式。Spring框架，特别是Spring Boot和Spring Cloud，是实现这一模式的首选工具之一，因其强大的功能和易用性而受到广泛欢迎。本书详细介绍了Spring微服务的相关概念、实践技巧以及最佳实践。在书中，作者John Carnell可能会涵盖以下关键知识点： 1. **微服务基础**：阐述微服务架构的核心理念，包括服务的定义、边界、通信方式以及为什么选择微服务架构。 2. **Spring Boot入门**：介绍Spring Boot的基本原理和优势，包括起步依赖、自动配置、健康检查和Actuator等特性，以简化微服务的开发和部署。 3. **Spring Cloud组件**：讲解Spring Cloud提供的服务发现（如Eureka）、配置管理（如Config Server）、API网关（如Zuul或Gateway）、负载均衡（如Ribbon）以及断路器（如Hystrix）等组件，帮助构建可扩展和容错的微服务系统。 4. **数据访问与集成**：讨论如何在微服务环境中进行数据管理，包括数据库的隔离、分布式事务处理以及使用RabbitMQ或Kafka等消息队列进行服务间通信。 5. **测试与部署**：介绍如何编写单元测试和集成测试，以及如何在Docker容器中部署和管理微服务，确保微服务的可移植性和可靠性。 6. **监控与日志**：讲解如何利用Spring Boot Actuator进行性能监控，以及如何集成Logback、ELK Stack（Elasticsearch, Logstash, Kibana）或Splunk等工具来收集和分析日志，以提升系统的可观测性。 7. **安全与身份验证**：探讨OAuth2、JWT（JSON Web Tokens）等技术在微服务中的应用，实现安全的API交互和用户认证。 8. **持续集成与交付**：介绍Jenkins、GitLab CI/CD或CircleCI等工具，实现自动化构建、测试和部署流程，以加速开发迭代。 9. **微服务治理**：讨论服务版本控制、回滚策略以及如何利用Netflix OSS（Open Source Software）组件进行服务治理。通过这本书，读者不仅可以学习到理论知识，还能通过实际案例理解如何将这些知识应用于实践中，从而成为一名熟练的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

PREFACE

xvi

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.

ACKNOWLEDGMENTS

xviii

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页未读，继续阅读

WNboy_2016

粉丝: 0
资源: 2

Spring微服务实战 - John Carnell

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

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

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

Spring_Microservices_in_Action_v8_MEAP

Spring in Action, 5th Edition.part1

spring 5 , Spring Boot 2.0,Spring cloud

深入实践Spring微服务

spring boot项目英文文献

matlab运用案例，用于学习

基于神经网络的流量异常检测高分项目+源码.zip

使用优化算法优化变分模态分解(VMD)算法的惩罚因子(α)和分解层数(K)python源码.zip

最新资源