Gavin Z.

1. Having a solid foundation in Java and a deep understanding of object-oriented programming, proficient in basic development techniques such as IO streams, collections, multithreading, reflection, generics, and network programming. 2. Deeply understand the design principles and underlying architecture of open-source frameworks such as Spring, SpringMVC, and Mybatis, and have researched some core source code. 3. Deeply understand the design principles and underlying architecture of open-source frameworks such as SpringBoot and SpringCloud, and have researched some core source code. 4. Deeply understand the Redis thread model, proficiently grasp the usage scenarios of Redis core data structures, be familiar with multi-level cache architectures, and be familiar with various high concurrency cache usage scenarios, such as cache avalanche, cache penetration, cache invalidation, and hotspot cache reconstruction. 5. Proficient in the use of common message middleware, has solved various difficult problems in message communication scenarios, such as message loss, message duplication, message sequence, and large-scale message backlog. 6. I have conducted in-depth research on high-performance IO communication models and related open-source components such as Netty, and am familiar with the Netty thread model. 7. Deeply understand the underlying principles of JVM, be familiar with the use of various garbage collectors and core parameter tuning in JVM, have some experience in online JVM tuning, and have unique insights into JVM tuning. 8. I have solved various technical challenges in distributed scenarios in the project, such as distributed locks, distributed transactions, and distributed tasks. 9. Familiar with commonly used design patterns, data structures, and algorithms in Java. 10. Proficient in tools such as Git, Maven, Docker, etc., to improve development efficiency. 11. Master basic knowledge of computer networks, familiar with network transmission such as HTTP, HTTPS, TCP, etc. 12. Master the use of commonly used Linux commands, Nginx reverse proxy, ECS environment deployment, and ElK log queries.