I am concerned about the week of technical developments 2015.10.25

Distributed System Practice

1. SCYLLADB: 10 times times better performance with C + + rewritten Cassandra

Http://blog.jobbole.com/93027/?hmsr=toutiao.io&utm_medium=toutiao.io&utm_source=toutiao.io

Point: Have been very dislike of the Hadoop series on the heavy dependence of the JVM, may be I am not familiar with Java, it is always felt that the JVM behind us do a lot of invisible work, the heart is not practical. SCYLLADB claims that the performance of the Cassandra is 10 times times higher, certainly with the removal of the JVM has a certain relationship, but not 10 times times, has to be user feedback.

2. building a streaming datacenter using Elasticsearch, Kafka, and Cassandra

http://mp.weixin.qq.com/s?__biz=MjM5MDAxNjkyMA==&mid=400110817&idx=1&sn= 60e21d161b592ef7331f0f44caa360b5&scene=0&key= B410d3164f5f798e490f3e4db23c5f11f864788c0dcfc73ab6fd4c666c699d7cd6d84faa2c3a707a356db637cdd63b88&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11.1+build (15B42) &version= 11020201&pass_ticket=yshqngdeh4%2bb2e7%2bx4w6%2flqs3l2erjr0i8zbysgpzp5s69gnocvdbprykw2rrdyt

Important: I've written several articles about elk in the previous weeks of sharing, which explains how to apply these open source components to your business systems, which is a good use case description

3. Qcon Shanghai Conference

Http://pan.baidu.com/s/1bndTOOv#path=%252F

Key points: Qcon Shanghai Conference All PPT, thank Yong Boss provide.

Service and resource management technology

1. Docker Registry V1 to V2

http://dockone.io/article/747

Important: The "editor's word" Docker Registry 2.0 version has been optimized for security and performance, and has redesigned the mirrored storage format. We will describe in detail the difference between Docker Registry V1 and V2, and on this basis share the real-time synchronous migration practices of the finches cloud.

2. The ins and outs of Docker commit

http://mp.weixin.qq.com/s?__biz=MzA4Nzg5Nzc5OA==&mid=400020522&idx=1&sn= b38e32b00c096b65998acd4b16b0f4d3&scene=0&key= B410d3164f5f798ecd072851bebf017010e9b7ece55820cf6760ade941e17d27cee073411dcf74363722dc9c67f9ebb8&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11+build (15A284) &version= 11020201&pass_ticket=5nj5pfbmsn4o9gekic%2bhocdzybohsz09kxwqrjobz0hhculnkacp0wuokl0x3t5g

Important: An in-depth understanding of Docker's principles must docker build start with a command and be docker commit docker build a prototype. The reason is simple, these two commands open up the entire process of Dockerfile to Docker containers, and then to the Docker image, almost covering the D All the concepts in ocker.

3. Container Cluster management behind Docker-from Borg to Kubernetes (ii)

http://www.infoq.com/cn/articles/docker-container-cluster-management-part-02?hmsr=toutiao.io&utm_medium= Toutiao.io&utm_source=toutiao.io

Key points: This article mainly introduces the part of Borg paper about improving the utilization ratio of resources, it can be said that this part is the essence of Borg thesis, and it is also the root reason of Borg to surpass any open source resource management system in the industry, if you read the Borg paper, it is difficult to read English. You can read this article carefully.

4. Docker Starter | A nice introduction to Docker

https://mp.weixin.qq.com/s?__biz=MzA5OTAyNzQ2OA==&mid=400048453&idx=1&sn= c72e356489b7696249b7216f8d6fc3dc&scene=0&key= B410d3164f5f798ea20ff1848015f1074bed7afa11a02d9efdf40ac3bd34eb9a5d820b701fa2ef3845b6a314e18e285b&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11+build (15A284) &version= 11020201&pass_ticket=2q56e2vmoqt2dhdnfsunvookxfjlxomcdibyhnbk9i0kqgbifjxe5ril0exytvj6

Important: {The author says} seeing the headline you might think, isn't there a lot of introduction to Docker on the Web? The same topic has been told many times, there is no need to talk about it? However, in my body this mixed arrogant and stubborn although disgust, but let me widely welcomed by everyone, which also makes me feel I should come to a one (article), haha.

5. Docker's practical exploration in League of Legends Games

https://mp.weixin.qq.com/s?__biz=MzA5OTAyNzQ2OA==&mid=400111438&idx=1&sn= 2a80432974e9e7f97ac604c619c0c1dd&scene=0&key= B410d3164f5f798e827ac0c590a964af6ca1ece8c29c1309902406052434a2faca1e5caae652c1938a0d41fea66e0d93&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11.1+build (15B42) &version= 11020201&pass_ticket=xtsnxi%2fn%2bgdvf%2fwviqzu4iuyg3v7vkjay%2bv%2f40qymgas3lehkc7ta7urbz%2flw91w

Important: This article describes how to implement container persisted data using a data volume container.

Service Scheduling and Trace technology

1. Micro-Service Annual summary, after reading this you should know how to answer other people's Questions

http://mp.weixin.qq.com/s?__biz=mza5odm0nja3na%3d%3d&from=groupmessage&hmsr=toutiao.io&idx=1& Isappinstalled=0&mid=400146790&scene=1&sn=5cba6e9f90db52dc6d9010c3237c1902&srcid= 1021xaf2qcrwy7oq7tuvwxpv&utm_medium=toutiao.io&utm_source=toutiao.io

Key points: The rise of container technology and PAAs platform let the idea of micro-services again into people's horizons, in the end should not adopt a micro-service architecture? In addition to its own business, the use of micro-services also requires a better foundation platform support.

2. flow control and token bucket algorithm

http://blog.jamespan.me/2015/10/19/traffic-shaping-with-token-bucket/?hmsr=toutiao.io&utm_medium= Toutiao.io&utm_source=toutiao.io

Important: This paper introduces the basic principle of flow control

DevOps Technology

1. Efficient Automated Operation tool Clip

http://mp.weixin.qq.com/s?__biz=MzA4Nzg5Nzc5OA==&mid=400028072&idx=2&sn= f7b7af17f8411b23fabc56fd6c573767&scene=0&key= B410d3164f5f798e706d3bae1285cd9ae2364b235d67624ae06b0b23720454f106fd510b39a847e554bfca263e66141b&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11+build (15A284) &version= 11020201&pass_ticket=scbzg37dovds7xg709xuvm8j9lll%2bcxctntvk0gedizqwtxgrr19%2flclhr7ye0nn

Point: The first few weeks to share the Clip tool introduction, this article introduced the clip installation and use of the method. The clip tool is designed to be very ingenious and can be integrated into the Beehive agent later.

2. continuous release of three anti-patterns and solutions

https://mp.weixin.qq.com/s?__biz=MzA4NjAzMjEyOA==&mid=400136141&idx=1&sn= 18a19b553115abe75479556d6d3c4b7f&scene=0&key= B410d3164f5f798e3365dc037c3f97bbd7c772d5c9a4aeddcd25b8d821e6225e8de23a1ec673c301586653e6599c35bb&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11+build (15A284) &version= 11020201&pass_ticket=scbzg37dovds7xg709xuvm8j9lll%2bcxctntvk0gedizqwtxgrr19%2flclhr7ye0nn

Important: This article describes the three anti-patterns of continuous deployment, namely: one. Manually deploy the software, two. Deployment to the class production environment after development is complete, three. Manual configuration management of the production environment.

3. create a people-oriented efficient operation and maintenance system

http://mp.weixin.qq.com/s?__biz=MzA4Nzg5Nzc5OA==&mid=400064858&idx=1&sn= 482a3a12d6d04833af575856097a0399&scene=0&key= B410d3164f5f798e66244737b7989fb33cc722779fbe306f18d3d316c25705a971634e88e1d6c9073b2c2d7633612123&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11.1+build (15B42) &version= 11020201&pass_ticket=yshqngdeh4%2bb2e7%2bx4w6%2flqs3l2erjr0i8zbysgpzp5s69gnocvdbprykw2rrdyt

Key points: "Often in the river Walk, which have not wet shoes," for often on-line operation of the students, it is difficult to make no mistakes, this shows that our system design is not in line with the "people-oriented" purpose to do. For example, the design of SMS, I have always admired OP students in the middle of the night can also hear the alarm message to deal with the problem of the ability to practice. If it is a voice alarm, I believe it will be much better. Again, such as Beehive original additions and deletions instances of the interface, must be existing instances of the metadata are all listed as parameters, resulting in the OP do not dare to operate, for fear of not wishing to modify the instance metadata to write wrong and caused an accident, soon we modified into an incremental interface, just enter the metadata of the instance to be modified, OP was relieved to operate. This is a lot of examples, please everyone in the design of a system or interface, multi-station in the user's perspective to train of thought, people-oriented.

Tools Collection

1. Teach you how to diagnose problems with Strace

https://mp.weixin.qq.com/s?__biz=MzA3MzYwNjQ3NA==&mid=400041851&idx=1&sn= c75d3cac697b3c234679239abfba83cc&scene=0&key= B410d3164f5f798e298d5f0dab3f2164d8958ea7af023861a2e43664f69c0f47be7c3960a290049c6fe5214c9b71d78c&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11+build (15A284) &version= 11020201&pass_ticket=5nj5pfbmsn4o9gekic%2bhocdzybohsz09kxwqrjobz0hhculnkacp0wuokl0x3t5g

Important: Strace can be used to track the function stack of system calls, while the strace count function can also analyze performance, this article tells you how to do it.

2. Code of Impressionism: write some good code

http://mp.weixin.qq.com/s?__biz=MjM5NzMyMjAwMA==&mid=400067207&idx=1&sn= 65d351f4b228800220ed7e5a2b13bb24&scene=1&srcid=1020h9igecu3sk9gyfl4cl5q&key= B410d3164f5f798e96e5696feb6f3a5b0c81c75edde782fcc094909f8b85628a1d93a11043e86e7d468645e47030d8a7&ascene=0 &uin=mjk1odmyntyymg%3d%3d&devicetype=imac+macbookpro11%2c4+osx+osx+10.11+build (15A284) &version= 11020201&pass_ticket=2q56e2vmoqt2dhdnfsunvookxfjlxomcdibyhnbk9i0kqgbifjxe5ril0exytvj6

Point: I believe that no one is willing to waste their lives to maintain a piece of garbage code, then start from their own, write some good code. What is good code? This document has a lot of examples to illustrate, see if you have reached the standard?

3. Pragmatic Technical Debt management

Http://www.infoq.com/cn/articles/pragmatic-technical-debt

Key points: I believe that all teams or systems have technical debt, the face of technical debt, complaining and blame is useless, blindly pay the debt or completely ignore is not feasible, we need to effectively manage it, and gradually eliminate, this article gives a lot of management technology debt recommendations very practical.

4. Detailed design pattern six principles

http://blog.jobbole.com/93248/

Key points: The design pattern is too complex, so many rules and regulations can not remember, so later people sorted out 6 laws, if the 6 laws are still not remember, I summed up a word, "on the Interface Programming", the 6 laws are about the interface, the variable part of the abstract interface, the object through the interface communication, All the changes occur on the implementation class of the interface, thus achieving the goal of high cohesion and loose coupling, and improving the iterative efficiency of the software.

I am concerned about the week of technical developments 2015.10.25