Now that I've had time to dig into both the docs, code, and concept, I reiterate my appreciation for @Idit_Levine and her team at @soloio_inc. SuperGloo is a service mesh orchestration layer which makes your underlying choice almost irrelevant. A thread:
I don't actually know if I fully love the concept of a service mesh because it appears to be trying to layer functionality on top of CaaS offerings in order to make it more like a PaaS.
Given the usability, availability, and maturity of PaaS platforms, I think that you should certainly use one if you need one. In fact, the cloud-native buildpack work, being done by the @CloudNativeFdn along with @heroku, may bridge the two worlds.
This is yet another technology choice with its fair share of tradeoffs and consequences. Again, so which one do you pick? Luckily, SuperGloo has come along and will go a long way toward making the choice nearly irrelevant. SuperGloo seems to support several.
You pick one which does what you want, and then throw SuperGloo in front of it and go from there. I love this concept, not just an orchestration layer, also an abstraction layer. I can't wait to see how this shakes out.
