I love when people can't tell the difference between a quick architecture discussion and Big Design Up Front (BDUF). Weeks of coding can save you hours of planning. A little prep for a development effort goes a long way! I think that, largely, folks like to hate on architecture because the BDUF they normally have seen is very anti-agile in that it doesn't actually increase agility.

One thing which has been really bothering me lately is running up against folks who insist on defining "value" in the narrow terms of that which can be directly observed by users' eyeballs. Isn't #agile supposed to know better? A thread. I'm legitimately confused about why anyone claiming to be #agile would be so myopic as to say that investing in the underlying technology platform, paying down technical debt, or training a team in a helpful technology is somehow less than "feature dev".

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.