"Depth" deep-dive into the principle of large Web site technology-Preface -0.0.1-snapshot

Directory

As the writing process iterates, if you see this article in the public number, you can read the latest catalogue by clicking on the original text.

• Order

The following is a sequential

0. Order

The previous article talked about the idea of building a personal knowledge system in the years to come, at the heart of self-awareness, from the depth of professionalism and the breadth of universal power.

I've been writing for a while, but the articles, including a series of multi-thinking models, are all about the cognitive aspects, and not much in their field of expertise, so starting with this article, I'll be writing an ebook for my area of expertise within the next 3-6 months .

After all, the work is the Internet development, the company is also a large Internet enterprise, so the theme is set as "large Web site technology principles." Based on past two years of work experience, and through reading professional books and some third-party information to accomplish this goal.

In fact, there is a similar book, "Large Web site technology architecture," but after all, personal experience is not enough to put the word structure, so the content of the book is more focused on the underlying principle, relatively less complex.

1. Writing outline

The following is a tentative outline of the book, which will continue to iterate as the writing process progresses.

2. Content Overview

This book is divided into three pieces: basic principles and thinking, core modules and system design.

2.1 Fundamentals and Considerations

In the field of software development, a variety of languages, frameworks abound, the previous years of big data, cloud computing and this year's AI is to the original fire computer technology added to the fire. But eventually original aim, some basic principles are interlinked.

For example, distributed systems have distributed databases, distributed cache, distributed services, distributed file systems, and so on, but some of their underlying principles, such as network protocol, load balancing, consistency algorithm and other ideas are the same.

This chapter will throw away the language and frame, return to the essence of computer technology, talk about the principle and some personal thinking.

2.2 Core Modules

The second chapter will take the main module of the large Web site as a starting point, such as distributed cache, distributed services and other modules. The various principles of the previous chapter will be presented in this chapter.

Of course, we will also delve into its principles, such as the caching strategy for distributed caches. There will also be more specific applications built on them, such as distributed session based distributed cache, distributed counters.

In the section on distributed services, we'll talk about the fundamentals of completing an RPC call, and also talk about how a highly available production-level service framework can perform the functions of monitoring, governance, and so on, and I'm also thinking about creating an RPC framework wheel for this idea.

2.3 System Design

Above the module is a complete system design, this chapter has not thought too much content at present.

It is mainly the lack of personal experience, especially the lack of a very systematic software architecture experience, it is more difficult to master the system architecture such a large theme.

At present, we have prepared a section: Design and thinking of high concurrency systems.

From the front end, to the intermediate service, and then to the underlying database to talk about how to design a system to deal with high concurrency, the typical scenario is a second kill.

3. Scheduling and other

Such a large project, the natural setting of a deadline.

The deadline for this book will be June 15, 2018.

That day was the day I had been working for three years, and by completing this book, I had reached the level of knowledge that a web developer with three years of experience would have in purely technical terms.

In this book tentatively 10~15 article, 8 months time to calculate, every two weeks to complete an article.

Aside from working days, plus writing general-purpose articles, the time allotted to each article should be every weekend day, two weeks and 16 hours.

Content will not be strictly followed by the outline from the later, content at any time iteration.

Can see here must be true love, you can pay attention to my blog, the public number or circle of friends, in the future, I implore you to help treatise technology Big coffee.

First Open

Original link: https://wchukai.com/article/technical-principles-of-large-websites-preface

This article was automatically synced to Cnblogs by Metaclblog on 2017-11-06 09:00:00

This article is based on knowledge sharing-attribution-non-commercial use-Prohibit deduction of 4.0 International License Agreement issued, reprint must retain the signature and link.

"Depth" deep-dive into the principle of large Web site technology-Preface -0.0.1-snapshot