Re: [I] Deployment Components [openwhisk]

["kcexn (via GitHub)" <gi...@apache.org>]

kcexn commented on issue #5454:
URL: https://github.com/apache/openwhisk/issues/5454#issuecomment-1833016104

   I've been having issues with the Community Slack too. 
   
   The OpenWhisk architecture has as key components:
   1. The Controller
   2. The Invoker
   3. A Database
   4. A Message Queue.
   (5). Optionally an additional Scheduler.
   
   Most of the features in OpenWhisk are implemented using Service Provider Interfaces (SPI), and so many components can be specialized towards a specific implementation depending on your particular operational environment.
   
   The `default' (or simplest) deployment, consists of:
   1. NGINX (load balancer)
   2. Controllers. (Authentication, Load Balancing, Scheduling Services)
   3. CouchDB (Database service)
   4. Kafka (Message Queue)
   5. Invokers (Container Management Services)
   6. API Gateway (Utilities for Exposing Web Actions)
   
   In response to your specific points,
   
   MongoDB can be used as an alternative to CouchDB by configuring it in the relevant properties files in the Controller and Invokers. [Template](https://github.com/apache/openwhisk/blob/master/ansible/templates/whisk.properties.j2)
   Redis is used by the API Gateway. [Documentation](https://github.com/apache/openwhisk/blob/master/docs/apigateway.md)
   Elastic Search can be used as an alternative action log store. [Action Log Store Documentation](https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#logging)
   
   and Etcd is used by the new Scheduler component, which is most useful if you are deploying OpenWhisk on top of a container orchestration engine like Kubernetes. A little bit of the scheduler documentation can be found [here](https://github.com/apache/openwhisk/blob/master/proposals/POEM-2-function-pulling-container-scheduler.md).
   
   I agree with your general remark that some of the documentation is a bit out of date and disorganized though...
   


-- 
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: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org