Foreword
In recent years, micro-services can be described as popular. In the business model is imperfect, in the case of very large scale impact of traffic, many companies have abandoned the traditional single architecture, embrace micro services. This model with independent development, independent of deployment, scalability, reusability of the advantages, but also brings the question: development, increase the complexity of the operation and maintenance. Some people feel better and convenient service micro-management.
However, with the Docker container technology and automation operation and maintenance and other related technology development, micro-services become easier to maintain. Therefore, the future development of micro-services will become more perfect, become the future direction of development of medium and large enterprise business architecture.
But micro-service architecture includes more than N optimization, N number of details, some coding friends, because the architecture of the reach front-line combat, seeing everyone else in the transition to the micro-service architecture, then he can only make day after day wheel.
Recently we put together a set of micro-service real documents, explaining very thorough. Share with you today. This information is particularly suitable for the following groups:
1. not used the micro-services technology, SSM will only use the traditional framework
2. Used Spring Cloud, Dubbo technology, but is limited to use, can not solve the basic problems encountered
3. Never systematic study of micro-service architecture, architecture design that is out of reach
4. understand for micro-services technology, but there is no practical experience designing high availability high concurrency
What have you learned after reading this document you will get?
- Understand today is the most fiery of micro Services Architecture principles and open source frameworks;
- Hit front-line micro-core technology services giant is equipped with insider knowledge;
- Compare their own knowledge to master the point you may say, the knowledge to help eliminate blind spots, reconstruction of knowledge.
The specific content of this book are:
- Basics
- Micro-service design principles
- Micro Services of Spring Boot
- Micro Services of Dcker
- Micro Services of Spring Cloud
- Spring Micro Cloud services of other frameworks
- Automated testing and quality management services of micro
- Micro Services of JHipster
- Automation of micro-services deployment
- Micro log collection and monitoring of service
- Complete example
- Micro-service core function is recommended
Basics: What is the difference between micro-service architecture, and monomer system, how to implement micro-services Why choose Spring Cloud, Spring Cloud Profile.
微服务设计原则：针对微服务的设计理念进行整理，包括服务如何折分、前后端分离、CAP 理论和CQRS等，是一个高层次的指导原则
微服务之Spring Boot：详细地介绍Spring Boot的开发，包括使用它的优缺点，以及在企业级开发中常用的工具包的整合，包括面向切面编程、Web 开发、文档管理和调度管理，最后结合Dubbo完成一个示例性的分布式工程。
微服务之Dcker：主要讲解Docker的基础操作，介绍微服务中所用到的容器相关的技术，最后给出通用的基于容器的私有云架构。
微服务之Spring Cloud：Spring Cloud实现微服务的几个重要框架进行展开描述，让读者了解注册中心、负载均衡、容错、分布式配置、网关和消息总线，能够完成开发层面的微服务架构。
微服务之Spring Cloud其他框架：对Spring Cloud的非核心框架进行介绍，包括Consul、ZooKeeper. 安全框架和数据流框架。
微服务之自动化测试与质量管理：主要对测试和质量管理进行介绍，测试部分包括单元测试、AB测试、旨烟和回归测试，质量管理部分主要使用静态代码分析，并且基于SonarQube对代码进行静态检查，以及分析代码的总体质量。
微服务之JHipster：对微服务的最佳实践JHipster进行系统的介绍，并且对JHipster部分内容做了处理，将在国内不是很流行的部分进行了处理，尽可能详细地介绍JHipster的应用和配置。
Automated Deployment of Micro services: mainly introduces automated deployment, because the purpose is not only to simplify the development of micro-services, but also to improve the operating efficiency of the entire team. So PW use and automated operation and maintenance is very important.
Micro log collection and monitoring of services: mainly on the APM log collection and monitoring system for online, the probability of problems is still very large, and how to quickly locate the first time to find the point where the problem is very important. APM part of the common monitoring tools were cited, focusing on Pinpoint, and the use of e-mail alerts have also been highlighted.
The full story: through a comprehensive explanation of PiggyMetrics, so that the reader can understand - a simple technical point of micro Services Architecture and Construction Principle included, and the actual deployment of micro-services, complete basic operation of the business.
Due to space limitations, only a small series where the actual information contained in this document is all unfolded, the need to obtain complete documentation ape faithful to learn, can help point a praise, backstage private letter: "learning" get.
Micro Services core functionality recommendation: to build technical points in the micro-service process may be involved to explain, including workflow engine, rules engine, scheduling system, a distributed configuration and single sign-on.
