Repository navigation
Arke 2.0
#163
Replies: 4 comments 1 reply
|
The complexity of managing state across the client connection, broker connection, publishing and consuming could be simplified if we use a Concurrent state machine with Connect being the parent with consume and publishing as child state machines. |
0 replies
|
I know we have ongoing work for Jetstream, it might make more sense for it to fall in Arke 2.0. We have also had discussions and initial design work for RabbitMQ AMQP 1.0, not sure if it should fall in Arke 2.0. I really don't want to wait that long for AMQP 1.0 though. |
1 reply
|
Should we change our security model? As a proxy we're pretty open to allowing any client to connect. Should we:
|
0 replies
|
Additional thoughts, although we could implement these without a major version increase:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
As we kick off planning for Arke 2.0, we want to focus on architectural changes that improve supportability, reliability, and scalability.
Use this thread to propose and discuss potential breaking or sweeping changes that warrant a major version bump.
All reactions