Netty is a treasure, you only know it after you use it. After reading this article, you will know how to talk to the interviewer. A salary increase is a matter of minutes. Simultaneously,
Netty is an essential skill for architects to build a foundation. In other words: “Netty is one of the thresholds that Java programmers must pass to get to the high-level.” Java programmers who have worked for several years will find that business development seems to be When you are crawling around in the SSH world, you will start to feel lost and feel that life is boring. At this time, it is better to study Netty in depth, you will find that work becomes more and more interesting, and the ability to think independently will gradually strengthen.
What is Netty
Netty is an asynchronous event-driven (NIO) network application framework for rapid development of maintainable high-performance protocol servers and clients. Greatly simplifies network programming such as TCP and UDP socket servers. Netty supports multiple protocols, such as FTP, SMTP, HTTP and various binary and text-based transfer protocols.
Netty core components
The main building blocks of Netty:
- Channel；
- Callback
- Future；
- Events and ChannelHandler.
These building blocks represent different types of construction: resources, logic, and notifications. Your application will use them to access
The network and the data flowing through the network.
Explain the profound things in a simple way
This part is divided into 7 parts. In order not to affect the reading, this article only shows part of the screenshot content, and the full content can be found in the collection method at the end of the article.
table of Contents:
- 01 Getting started with Netty
- 02 Netty server creation
- 03 Netty client creation
- 04 Sending and receiving of Netty messages
- 05 Netty thread model
- 06 Analysis of Netty Architecture
- 07 Netty Case Collection
1. Getting started with Netty
- 1.1 Traditional BIO programming
- 1.2 Pseudo asynchronous I/O programming
- 1.3 NIO programming
- 1.4 AIO programming
- 1.5 Comparison of several I/O models
- .......
Two, Netty server creation
2.1 Netty server creation sequence diagram
2.2 Netty server creation source code analysis
2.3 Client access source code analysis
Three, Netty client creation
3.1 Netty client creates sequence diagram
3.2 Netty client creation source code analysis
Four, Netty message sending and receiving
4.1 Asynchronous read operation
4.2 Asynchronous message sending
Five, Netty thread model
5.1 Reactor thread model
5.2 Netty threading model
5.3 Best practices
Six, Netty architecture analysis
6.1 Logical architecture
6.2 Key architectural quality attributes
Seven, Netty case highlights
7.1 Memory leak class
7.2 Performance bottlenecks
7.3 Thread expansion class
7.4 Client connection class
7.5 Thread Safety Class
7.6 Message receiving class
7.7 Performance data statistics
7.8 Initialize the startup class
Summary: How to further learn Netty
Netty is a low-level network communication framework. If you only realize the IM function, you don't need to understand it deeply.
If you use Netty as the bottom layer of rpc or microservices, I think you are mainly concerned with the characteristics of Netty under high concurrency and various design concepts. You can look at the implementation of the finagle framework and see how finagle is doing How to deal with failure, how to retry, how to avoid retry storm after retry, and how to deal with back pressure, I personally think that learning other people's practices should be combined with my own functions, such as 50-50. I think all functions can be done, but in the environment of super concurrency, what problems will happen to this function and how to solve it is a problem that back-end programmers should pay attention to.
Netty must ask interview questions (including answers, important)
1. What is the difference between BIO, NIO and AIO?
2. What is the composition of NIO?
3. What are the characteristics of Netty?
4. Netty's threading model?
5. The reasons and solutions for TCP sticking/unpacking?
6. What kind of serialization protocols do you know?
7. How to initialize the client?
8. Talk about zero copy of Netty?
9. When was DefaultChannelPipeline created?
10. The Netty framework itself has the problem of sticky package and half package?
11. How does Dubbo avoid sticky packets and half packets when using Netty for network communication?
12. How to use the package separator DelimiterBasedFrameDecoder to solve the sticky package and half package problem? What is the principle?
........
Netty must ask interview questions (including answers)
If you need the above information, please remember to forward this article for me, follow me and reply [learn] to receive it for free!
Friends who have obtained the information, please make good use of it, don't be ashamed, and don't learn to cope with the interview, because this kind of learning is not very effective, you must understand it thoroughly and combine actual combat to operate, so that it can grow.