Introduction to the
Read the official soul documentation to get an overview of soul’s features and related concepts
tips
I need to have a general understanding of the functions of the gateway, read the official document of soul for two times (the first time read through, can understand how much, the second time refer to the basic concepts of gateway, organize my understanding of the concept of soul), organize roughly as follows:
The Demo should understand the general components of a gateway, as shown above in Gateway versions 1 and 2:
- Server: A server that listens for requests
- Router: Determines whether the request can match the backend service. If the request can match the backend service, the system continues
- Filter: You can perform some timing functions, such as adding, deleting, modifying and querying the header content of the request and response, and higher-order functions, such as traffic limiting and fusing
- Client: sends a request to the background service and receives a response
Read on and discover that Soul’s routing rules are dynamically generated. A key, foundational plugin is Divide. The configuration of these routes is saved in the Soul Admin module, the core module of the gateway is still Soul Bootstrap, and the forwarding and processing is still this
If Soul Admin is the configuration center, you can configure the Router and Filter
Read the data synchronization section briefly to see that Soul configuration can be dynamic
If you’re looking for something that’s familiar to you, use an analogy
Of course, there may be some descriptions and perceptions that are wrong, but these are all preconditions for correct understanding, and we can update our models through constant reading and research (I still don’t fully understand Soul).
Just like now we have a map, some places can be demolished and rebuilt, but we can still explore this map, go to the destination, in the process of exploration, constantly improve our map