Hi Thomas, Proposal looks good and consolidates various ideas discussed so far. Would have a closer look. Have a quick query for now
> Since the front-door schedules round-robin or least-connected Is this routing round robin for per namespace + action name url or is it for any url? For e.g. if we have controller c1-c3 and request come in order a1,a2,a3, a1 which controller would be handling which action here? Chetan Mehrotra On Fri, Jul 13, 2018 at 10:59 PM, Markus Thoemmes <[email protected]> wrote: > Hello OpenWhiskers, > > I just published a proposal on a potential future architecture for OpenWhisk > that aligns deployments with and without an underlying container orchestrator > like Mesos or Kubernetes. It also incooperates some of the proposals that are > already out there and tries to give a holistic view of where we want > OpenWhisk to go to in the near future. It's designed to keep the APIs stable > but is very invasive in its changes under the hood. > > This proposal is the outcome of a lot of discussions with fellow colleagues > and community members. It is based on experience with the problems the > current architecture has. Moreover it aims to remove friction with the > deployment topologies on top of a container orchestrator. > > Feedback is very very very welcome! The proposal has some gaps and generally > does not go into much detail implementationwise. I'd love to see all those > gaps filled by the community! > > Find the proposal here: > https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+future+architecture > > Cheers, > Markus >
