divijvaidya commented on PR #13437: URL: https://github.com/apache/kafka/pull/13437#issuecomment-1490628418
> CopyOnWrite is quite inefficient compared to persistent collections I agree on this that persistent collections are more performant than standard Java `CopyOnWrite`. But we also, need to consider the impact of taking a dependency over a new project. Hypothetically (I haven't looked at the community of the two projects that you propose), let's say we end up using a dependency which is maintained by a single person and they decide to stop maintaining it. That leaves us with a choice to either overhaul our code base and remove all usages of that library (which I expect to be very intrusive for locking data structures) or take over ownership of something that we as a community are not experts in. To de-risk this, we would probably prefer libraries which have a strong community (such as Apache projects) or have prevalent in majority of the modern architecture such that the scenario of development contonuity stops being a risk (e.g. netty). Since you mentioned, "authorizer is quite read-heavy with very infrequent writes", and given the above risk highlighted above, would having slow writes with `CopyOnWrite` be an acceptable trade-off? I am curious to hear what others in the community have to say about this. cc: @ijuma @dajac @mimaison, perhaps you folks might be interested in this discussion. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
