Less code, more hair

This article has been included in GitHub, welcome everyone to participate in star and issues.

https://github.com/midou-tech/articles

Say something nonsense

I wrote a brief introduction of Es at the beginning. Regardless of the principle, I first ran two articles about Es, which received a good response. Some readers are also urging the following update progress.


In a group of 400 people, asking me to update is just too much pressure…


Actually, it’s fine. It tells us two things

  • The article has been read by everyone
  • There is something in the article

I just entered a new working environment recently, so I need to understand the new work content, understand the requirements and understand the engineering architecture. I have a lot of work to do.

I’m writing the Elasticsearch series at the same time as I’m learning it, there’s a lot of uncertainty and a lot of data to look up.

How about some body

Since it is learning, we must make a good learning route for ourselves, comb down the knowledge we want to master, and later learning will not be lost.

In addition to the front said to write this series of articles, there is no specific outline, can not help laughing at their own.

Spent some time summarizing the entire knowledge framework for Elasticsearch, which was later updated as a writing framework.

If you can’t see clearly, you can reply to ES brain Map to get hd PDF files.

This brain map is not only a writing roadmap, but also a good learning roadmap, as well as an ES overall knowledge framework.


The next few articles will be about how a user can use Elasticsearch, using some common examples.

For example, how to write large amounts of log data into ES? How do I create an index after I write it in? How do I query the data I want?

– It will be written around this series, using Elasticsearch first and then exploring how it works.

Elasticsearch

  • Elasticsearch

  • Forget the principle. Run first

Lue.