4 ms·

what are people's main gripes with the cloud native landscape?

• mrweasel 5y ago
  At best it's pointless. Everything is apparently cloud native, so why even bother? At its worst the cloud native landscape is complexity nightmare. Why are there 12 API gateways? Are they all equally good? They certain don't do the same, well mostly they do, have fun figurering out which one to use. Almost none of the product are named all that well, so that's no help. Right now the cloud native landscape is just a collection of pretty icons that look kinda cool. It doesn't really mean anything. Best I can tell: Graduated doesn't even mean that you're guaranteed that these product will work together... They might. I get that others look at the cloud native landscape and see endless possibilities, a smorgasbord of options, and that's wonderful. I just see complexity, confusing, and shameless self-promotion in an attempt to ride the Kubernetes/container wave and make a name for yourself and maybe a few bucks. Don't get me wrong, many of these tools are fantastic, but that some people can look at that massive graphic and think that the industry is moving in the right direction it troubling. Half of these product are dead-ends. We just don't know which yet. The room for mistakes are enormous and some poor soul will pick the wrong API gateway and be stuck with it for the next ten years.
• caniszczyk 5y ago
  complex, too much content/options for end users to decipher... e.g., "hellscape"
  • cfors 5y ago
    Surely, this is the very definition of too many options? *Disclaimer: Mostly happy user of many of these projects
  • rl3 5y ago
    >complex, too much content/options for end users to decipher... e.g., "hellscape" So basically an accurate representation of the market. :)