GitHub user mengw15 edited a comment on the discussion: Refactor: Decoupling
Direct Database Connection From ComputingUnitMaster & ComputingUnitWorker
Agree Design B feels more natural — CU as a pure executor feel clean.
Two questions:
**1. Effort & transition.** How big is the change of design B? Could we land
Design A first (DB-credential removal, small delta) as a stepping stone, then
evolve to B without a big-bang switchover?
**2. Who orchestrates?** In Design B's current sketch the frontend coordinates
compile → eid allocation → CU dispatch. That makes the frontend a critical
control-plane component, which feels off to me. Would it be worth introducing a
thin Execution Service that owns this orchestration? Any client would then just
call `POST /executions {wid, cuid}` and the Execution Service handles compile /
eid allocation / CU dispatch internally.
GitHub link:
https://github.com/apache/texera/discussions/5295#discussioncomment-17113924
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
