Introduction to "Building a background service architecture for small and medium-sized internet companies"

This series of articles is mainly about how to build a small and medium-sized Internet company background service architecture and operations architecture courses, the series of articles are the most widely used technology and tools.

The techniques and tools of this article series are as follows:

Background Service Architecture: Dubbo, Spring-boot, Spring MVC, Spring-security-oauth2, SPRING-LDAP, SPRING-DATA-JPA, etc.

Project management tools: Maven, Nexus

Version management tools: Gitlab, Git

Databases: MySQL, MongoDB

Operation and Maintenance monitoring tool: Open-falcon

Log management tool: ELK

Continuous integration tool: Jenkins

Collaboration tools: Confluence

Cache: Redis

Message middleware: Kafka, ROCKETMQ

Web server: Tomcat, Nginx

Container Engine: Docker

The process for this series of articles:
1, first introduce everyone already familiar with the Dubbo technology system, combined with Dubbo to build a complete technology framework based on restful

2, combined with Dubbo's restful framework, plus OAUTH2-based token verification, and the realization of a unified User Center design

3, focus on spring boot, and then combined with the previous Dubbo technical framework to transform, to achieve the spring boot and Dubbo Fusion

4, as a technical framework is definitely involved in Java performance tuning, so then according to the diagram to explain a series of things in the JVM, to help you fully understand the JVM

5, explain the message middleware Redis, as well as the high availability of cluster construction, as well as the data types, distributed and consistency issues

6, Git, elk, Jenkins, Confluence, Kafak, ROCKETMQ Tools installation Explained

7, explain the operation and maintenance of monitoring tools open-falcon, how to ensure timely notification operations and developer server problems, to ensure that the server and service uptime

8, the Docker series of courses, combined with Docker deployment

Architecture explains the goals of the design:

1. Low cost: The value of any company exists in order to obtain business benefits. If possible, expect everything to be low cost.

2, High performance: Site performance is an objective indicator, can be embodied in the response time, throughput and other technical indicators. System response delay, refers to the system to complete a function to use the time, the system's throughput, refers to the system at a certain time the amount of data can be processed, usually can be measured by the total amount of data processed per second of the system, system concurrency, refers to the ability of the system to complete a function at the same time, usually also with the QPS per second) to measure.

3. High Availability: System availability (availability) refers to the ability of the system to provide services correctly in the face of various anomalies. The availability of the system can be
It can be measured by the ratio of the time of the system outage to the time of the normal service, or by the ratio of the number of failures of a function to the number of successes.

4, easy to stretch: Focus on linear expansion, whether it is easy to join the machine to handle the rising user access pressure. System Scalability (scalability) refers to the characteristics of distributed systems that increase system performance (throughput, latency, concurrency), storage capacity, and computing power by expanding the size of the cluster machine.

5, High Security: Now the business environment, often appear by the site is towed library, user accounts stolen and so on. The security of the website is self-evident.