In my early days of Apple, I remember talking about things like "good
implementation of a bad idea" and "bad implementation of a good idea". In
this case, Promise Theory is the good idea.
What do you think about Promise Theory outside the scope of just pure CM?
Examples
- Container Choreography
- Habitat - uses promise theory in bash (maybe not most intuitive,
but with keep it simple w/ bash variables approach)
-
https://techcrunch.com/2016/06/14/chefs-new-habitat-project-wants-to-make-applications-infrastructure-independent/
- https://www.habitat.sh/docs/continuous-deployment-overview/
- InfraKit (https://github.com/docker/infrakit/) - seems that aspects
are Promise Theory.
- Service Discovery
- Consul (https://www.consul.io/) - with consul agent, can implement
Promise Theory w/ dyanmic async distributed config, though how that
config
happens is up to implementer.
- JavaScript:
-
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise
- https://davidwalsh.name/promises
- https://www.toptal.com/javascript/javascript-promises
It would be interesting to see a DSL parser in Go and Rust as open source
as these languages are becoming popular for distributed computing trends in
cloud computing, especially with microservices. If I had the skills of
compiler designer, I may be bold to implement it.
Could HashiCorp HCL (https://github.com/hashicorp/hcl) be used to represent
promises? They use it for their Terraform product
(https://www.terraform.io/), which is a CM but strictly for RESTful API,
like AWS or GCE.
--
You received this message because you are subscribed to the Google Groups
"dev-cfengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dev-cfengine/b7d41efe-62e2-49f7-a507-cd502c865809%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
