Add a blog post about the Routing POC#259
Conversation
Signed-off-by: Tom Bentley <tbentley@redhat.com>
|
|
||
| The big picture of what we've done breaks down like this: | ||
|
|
||
| 1. Preparatory internal refactoring to break apart a single state machine into two: One state machine for the client-proxy interaction, and a separate one for the proxy-broker interaction. |
There was a problem hiding this comment.
Feels funky to lead off the internal refactoring I think I can name every person that cares about this...
I agree its an important enabler but doesn't feel important to readers of the blog.
| We think this is pretty cool, and we wanted to let people know that we're actively working on this. And being open source, we wanted to remind people that they can [join us](https://kroxylicious.io/join-us/) and get involved in any of the following ways: | ||
|
|
||
| * Tell us how you'd use the Router API: We have some ideas for other routers we want to build, but maybe you have an idea that only makes sense in your company. That's OK — not every router needs to be general-purpose. Kroxylicious is built for exactly that kind of bespoke use case. | ||
| * Tell us how you'd use a topic router. What Kafka features does it need to support? What functionality does it need for operators? |
There was a problem hiding this comment.
Is it really a topic router? I get the need for a pithy short hand just struggling a bit with this particular one.
There was a problem hiding this comment.
Topic router" has an ambiguity — it reads as "router for topics" (as if the topics are moving) rather than "router that routes based on topic membership." Two alternatives worth considering:
- Topic dispatcher — names the mechanism honestly. Dispatcher implies "sends to the right place" without overpromising.
- Topic federation — names the user capability. Federation is well understood in distributed systems (DNS, LDAP, identity) and implies unified access to distributed resources.
I'm genuinely unsure which is better. Thoughts?
(Aside: federation does open up the option of naming the route selection components after Star Trek captains — Kirk, Picard, Janeway...)
2 participants
No description provided.