Refactor out Internal Core into Separate Projects

[sirinath]

Is it possible to factor out the internal core technologies used like in projects like:

• https://github.com/infinit/elle
• https://github.com/scylladb/seastar
• https://arrow.apache.org/
• https://calcite.apache.org/

This way these frameworks can be used else where and will get contributions separately. Also parts of the the architecture and design decisions gets validated and scrutinised better. Also this will limit ad hoc workarounds.

I am not familiar with the internals but ideas of core libs that can be present:

• coroutine / threading
• networking / RCP
• distributed consensus
• futures / reactive programming
• storage engine
• query planning
• etc.

[AtnNn]

Hi @sirinath,

You've opened a lot of very general, open-ended feature requests like this one over the past few weeks: #6300 #6299 #6298 #6297 #6287 #6286 #6285

Your ideas seem good but they aren't easily actionable and the motivations you give are too general. I recommend posting these ideas on our mailing list instead, or discussing them over slack.

Feature requests are a lot more helpful if they are more focused, if they provided more concrete motivations and benefits.