41 posts
Today I suddenly noticed a new badge on my GitHub profile, 'Arctic Code Vault Contributor' — which translates to 'Arctic Code Vault Contributor' — so I looked into this Arctic Code Vault.
GitHub Actions is a continuous integration service launched by GitHub in October 2018. I used Travis CI before; yesterday I tried GitHub Actions and found it more powerful with more to play with, so I'll share my first impressions.
The well-known game company EA (Electronic Arts) made a splash on GitHub, open-sourcing part of the source code of two games in the Command & Conquer series! The two games are: Tiberian Dawn and Red Alert.
Linus Torvalds announced the release of Linux 5.7 on the kernel mailing list. In his release announcement he commented: "So last week we were fairly calm, with no screams of 'let's drag out one more rc'. Fingers crossed — hopefully we won't have another situation like in 5.6, where a wifi regression landed at the last minute."
According to foreign media ZDNet, a Huawei L20 chief security expert published a Linux kernel hardening patch called HKSP on GitHub. Interestingly, the patch was quickly found by the development team grsecurity to have an "easily exploitable" vulnerability, immediately sparking heated discussion.
Google, the world's number one search engine, has long supported webmasters proactively pushing pages, but not through a visual interface for ordinary users — it is done via a programming API. Many webmasters are not professional developers, and because Google requires verifying site ownership, I cannot simply build a visual interface where webmasters enter their own keys. So I wrapped Google's API in a secondary layer to lower the difficulty of using it.
If you have followed me from the first section to create the project and tried running my code (https://github.com/NeilRen/SpringCloudDemo), I believe you can now build a basic microservices architecture. Since this is a beginner tutorial, many things are not covered in depth or detail — the goal was simply to get a microservices architecture up and running. If I have time later, I will try to write an advanced tutorial covering Spring Security, message queues, database distributed master-slave setups, distributed log collection, and so on.
After the previous section on service tracking and link monitoring, the basic microservices framework is nearly complete. Deployment in a microservices setup inevitably involves Docker, so how do we build a Docker image? In this section we'll cover packaging the code into an image file and uploading it to an image repository.
In the previous section we covered circuit breaking and degradation, and we can basically build a fairly complete microservices architecture now. But a microservices architecture is distributed — each service runs independently while depending on others — so if a problem occurs, it's hard to trace where it is. We need a service-tracing solution, and Spring Cloud Sleuth provides service tracing and link monitoring.
In the previous section we covered the API gateway, which lets multiple services be published uniformly through the gateway. Before publishing, we also need to understand a mechanism in microservices — circuit breaking and service degradation, called Hystrix in Spring Cloud. This section integrates Hystrix to implement circuit breaking and degradation. Hystrix has many features; we only cover the most commonly used circuit breaking and degradation mechanisms.
