Hi, I’m crooked.
Surfing on Github a few days ago, I found two treasure troves.
I don’t hide the secret, take it out to share with you.
The two treasures are arthas and SOFARegistry, both of which are ali open source projects.
Arthas is a Java diagnostic tool developed by Ali.
And what is SOFARegistry? Haven’t heard much about it?
I haven’t been around that long, but I kind of know what it is, and I think it’s a wheel, but it’s a pretty good wheel.
Take your time. I’ll give you one in a minute.
arthas
Arthas, I can’t remember how many times I’ve mentioned it in my previous posts. Basically, it is about the use of practical operation cases or official training Demo.
It is also very widely used:
So what treasures did I find on Github?
Hidden inside its issue Labels:
Click on Labels and you’ll find a label called User-case:
Issues under this TAB is the first treasure I want to talk about:
Github.com/alibaba/art…
I’ll take a screenshot of the first page and see if you have a strong desire to click through and see what it is:
For example, let me show you this user-case from ICBC:
Github.com/lyghzh/pub/…
I actually thought that Arthas was a dangerous thing for people to do in production.
It is a double-edged sword, use good, leave work early, use bad, maybe back a production accident.
So, take the choking approach and don’t use it at all.
Icbc, as a bank, in this regard certainly more consideration.
In their landing difficulties, the first is the issue of “information security”, which is their basic red line, but also the root of the bank:
So how does it use Arthas in production?
In this case, the answer to this question is given.
We have designed a lightweight architecture that allows developers to easily and intuitively use online diagnostic capabilities in a Web UI. So what did we do?
Based on Arthas’s capabilities, a Web UI page is encapsulated again, and the interface behind this page can be tailored and modified, processed into JSON data and sent back to the platform for presentation.
In addition to introducing the overall architecture, the article also provides the effect of practical use.
The control panel, for example, looks familiar:
Based on Arthas’s native response, a presentation page was created.
The data on this page was returned by Arthas:
There is also the ability to decompile:
But I don’t see anything about hot loading in the article, so I’m guessing that such dangerous features are blocked from the Web page.
Under this issue, I found another similar project mentioned:
This is a Java application diagnostic tool for go Where open source:
It doesn’t stretch. I can’t learn it.
Or take this case:
Github.com/alibaba/art…
Then he used a time-consuming method of tracing a little bit, and then repaired a little bit.
After four optimizations, the call link time of the same request was reduced from 343ms to 27ms. Isn’t that nice?
Then, he came to the conclusion, which is the point of this optimization:
You can see that it’s not really any big optimizations, it’s just some of the little things that we normally use.
Finally, he wrote a “strong recommendation” : A ramble on dynamic tracking technology.
Okay, this is another site THAT I bookmarked a long time ago. I shared it with you:
Blog.openresty.com.cn/cn/dynamic-…
This blog is written by Yichun Chang, founder of the open source project OpenResty, and OpenResty Inc. The founder and CEO of the company.
I mean, the big guy endorses and reads.
I’ve just picked two cases out of the first trove, and you can dig the rest.
SOFARegistry
What is SOFARegistry?
In fact, I understand it as a registry wheel. Or to be more specific, Eureka with Ali characteristics.
Here’s its Github address:
Github.com/sofastack/s…
Do you see the Sofastack in it?
SOFARegistry is just a piece, Sofastack is the board.
This is a Stack, a technology Stack, and an architecture scheme in the financial field.
There are many projects under it, from the name of the main project, such as xxxBoot, xxxRPC, xxxRegistry, you can see that we can build a complete project with these projects:
About SOFARegistry’s treasures also hidden in its Labels:
Github.com/sofastack/s…
This Label, called Event/source-code-Analyze, is full of source code analysis.
In addition, it is an officially initiated activity, and the content of the article will be reviewed by special personnel to ensure accuracy:
There are nine source code parsing tasks released:
There are high and low levels of difficulty. There are different reward measures according to the difficulty of the task:
The opportunity to become a Contributor or Member in the community is quite attractive.
For example, let’s take a look at this task for data inversion indexes:
Github.com/sofastack/s…
Its issues description also indicates what to write and which parts of the code to look at.
The directions are very clear.
The final parsed article submission format is MD:
We can just download it and read it.
This will be a good entry point for those of you who want to understand SOFARegistry better.
Although SOFARegistry knows the wrong person, I want to write about SOFARegistry’s activities so that more people can know about them.
Because I think this activity is very good, source code parsing, I see a new way to participate in open source projects.
Finally, what do you tell me about these two treasures?
It tells me to pay more attention to Labels when shopping for open source projects. You might be hiding something good. I used to pay very little attention to Labels anyway, and I always thought that only project maintainers cared about Labels.
Finally, this article is published on the public account [WHY Technology]. Welcome to pay attention to it, Bixin.