You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/10/10 06:26:34 UTC

[GitHub] markusthoemmes commented on issue #2254: Reevaluate the need of Consul in our deployment

markusthoemmes commented on issue #2254: Reevaluate the need of Consul in our deployment
URL: https://github.com/apache/incubator-openwhisk/issues/2254#issuecomment-428452922
 
 
   To make things a little bit more clear:
   
   As mentioned in the introductory post, Consul was never used for its feature richness in OpenWhisk. Rather, we used to use it as a mechanism for state sharing and configuration storing.
   
   The state sharing has been eradicated for various reasons (performance and correctness being the most significant ones). The current OpenWhisk architecture has a lot cleaner cut concerns when it comes to where the state lives and how its built up.
   
   The configuration storing bit of it was just plain annoying and non-standard with regards to how deployment tools like ansible work. It also made for further deviation from alternative deployment mechanisms (Compose, Kube, Mesos).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services