4 ms·

Nice to always see this on HN... we have more landscapes out there too :) https://landscapes.dev https://landscapes.dev There are also two sub landscapes in t

Nice to always see this on HN... we have more landscapes out there too :) https://landscapes.dev https://landscapes.dev There are also two sub landscapes in the CNCF landscape in case you're interested: https://landscape.cncf.io/serverless https://landscape.cncf.io/serverless https://landscape.cncf.io/wasm https://landscape.cncf.io/wasm (still in beta) There's also a secret feature that shows who is raising funding etc in the space: https://landscape.cncf.io/funding.html https://landscape.cncf.io/funding.html Anyways, I know people like to hate on the cloud native landscape but the reality of the situation is that there is a large healthy competitive ecosystem out there and a lot of options.

j_french 5y ago
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. :)
qbasic_forever 5y ago
How do you measure or understand the end user usability of these landscapes? Because I actually like the content in them but am just totally baffled and annoyed at trying to use it. A text table I could slice and dice with a few dimensions would be infinitely more usable.
fudged71 5y ago
These landscape diagrams are fantastic, available in multiple formats, open source, and look great. I wish every market landscape was formatted the same way. Any plans to make a "landscape generator" tool of some sort available for non-coders?
deleted 5y ago
[deleted]

j_french 5y ago

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. :)

qbasic_forever 5y ago

How do you measure or understand the end user usability of these landscapes? Because I actually like the content in them but am just totally baffled and annoyed at trying to use it. A text table I could slice and dice with a few dimensions would be infinitely more usable.

fudged71 5y ago

These landscape diagrams are fantastic, available in multiple formats, open source, and look great. I wish every market landscape was formatted the same way. Any plans to make a "landscape generator" tool of some sort available for non-coders?

deleted 5y ago

[deleted]