1, bind the click event twice to the submit button
2, curcuit breakers are not in use when automatic retries are in place
3, if there are more than nine files, you shouldn't use "?", you should use "*", for example,
zgrep 'searchItem' */portal-2019-08-14-*.log.gz
4, when you are using vim, "/" to search forward from the cursor position, "?" to search backward from the cursor position, "N" to find next, "Shift + N" to find previous, "G" to move to the first line, "Shift + G" to move to the last line. VIM can also open .tar.gz files, for example:
vi /applog/tomcat_portal/17/portal-2019-08-14-1.log.gz
5, Intellij IDEA's module production directory:
when you run a project based on that module, you will need to compile the entire module and put the compiled result in a directory so that your tomcat container can take advantage of the compiled content to run the web application.
6, compress
tar -zcvf weChat_portal.20190816110301.tcj.tar.gz weChat_portal
-z: To create a compressed gzip archive file;
-c: Creates a new .tar archive file.
-v: Verbosely show the .tar file progress.
-f: File name type of the archive file.
7, uncompress
uncompress in the current directory:
tar -zxvf weChat_portal.20190816110301.tcj.tar.gz
uncompress to another directory:
tar -zxvf weChat_portal.20190816110301.tcj.tar.gz -C /home/weixn/myDirectory
8, microservice: easy to develop, deploy and scale (Auto-Scale, which creates instances when requests are frequent, and which destroys instances when requests are rare). High coheson, low coupling. But because there are so many instances running on the cloud, it's very difficult to operate and manage the relationship between the instances.
monolithic: difficult to quickly develop and deploy, because there are so many co-dependent services. And it's difficult to scale: because all packages and services rest inside a single large monolithic application, when you scale a single service in high demand (high concurrency), you have to scale the entire application, which is slow and less agile.