Find Those Routes!
AssumptionsPermalink
- You have my-http-server deployed with route registrar routes setup from the previous story
WhatPermalink
In this story you are going to follow how route registrar registers routes (say that 5 times fast).
In the HTTP Routes section you learned how the Route Emitter on the Diego Cell repeatedly sends route registration messages to NATS. Then GoRouter subscribes to those NATS messages and then populates its route table. The same thing happens with component routes. But instead of the Route Emitter emitting routes (teehehe), it’s Route Registrar that is emitting routes repeatedly.
HowPermalink
🤔 Look at NATS
- Subscribe to the the NATS messages for your component route from the
my-http-server VM.
- You can find the NATS username, password, and host on the my-http-server VM
at
/var/vcap/jobs/route_registrar/config/registrar_settings.json - See the story Route Propagation - Part 3 - Route Emitter and NATS if you need help.
- ❓ How do the component route NATS messages compare to the app route NATS messages?
- You can find the NATS username, password, and host on the my-http-server VM
at
🤔 Look at the routes table
- Bosh ssh onto the router VM.
- Look at the GoRouter routes table and find your component route.
- See the story Route Propagation - Part 4 - GoRouter if you need a reminder on how to this.
- ❓How does the component route compare to the app routes?
❓ Bonus QuestionPermalink
So if GoRouter routes off-platform users to other components, how do off-platform users route to GoRouter?!?!
Expected ResultPermalink
There are (almost) no differences between the app routes and the component routes. GoRouter does not know the difference between them and treats them the same.