> If we want to bring groups/containers/etc into the default deployment > mechanisms of C*, great. I am all for dividing it up into micro services > given we solve all the problems I listed in the complexity section. > > I am actually all for dividing C* up into multiple micro services, but the > project needs to buy in to containers as the default mechanism for running it > for that to be viable in my mind.
I was under the impression that with CEP-1 the project did buy into the direction of moving the workloads that are non-latency sensitive out of the main process? At the time of the discussion folks mentioned repair, bulk workloads, backup, restore, compaction etc ... as all possible things we would like to extract over time to the sidecar. I don't think we want to go full on micro services, with like 12 processes all handling one thing, but 2 seems like a good step? One for latency sensitive requests (reads/writes - the current process), and one for non latency sensitive requests (control plane, bulk work, etc ... - the sidecar). -Joey
