Cloud Native Interactive Landscape
landscape.cncf.io
landscape.cncf.io
There are also two sub landscapes in the CNCF landscape in case you're interested:
https://landscape.cncf.io/serverless 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
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.
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.
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.
So basically an accurate representation of the market. :)
*Disclaimer: Mostly happy user of many of these projects
If you want to develop a cross cloud app with autoscaling, self healing, health checks, service discovery, network policies, etc then you're going to have complexity. The question is whether you want to invent it yourself or use a platform like k8s
I'm not sure I disagree with you but I also understand why they might be there.
Many (most?) of the things are tied to organizations and they try to show information on those organizations.
The CNCF doesn't have certified partners. It is a sub-foundation of the Linux Foundation and a non-profit. The CNCF does have members. Some of them are vendors and some are end users. Things listed in the landscape don't need to be from a member.
FYI it's also an open source project that others can use and build upon! https://github.com/cncf/landscapeapp
That’s scary.
Seems like this isn’t really saying anything. But maybe useful to find things to look at further?
From the Wikipedia pager for JCL:
"Job Control Language (JCL) is a name for scripting languages used on IBM mainframe operating systems to instruct the system on how to run a batch job or start a subsystem.[1]
More specifically, the purpose of JCL is to say which programs to run, using which files or devices [2] for input or output, and at times to also indicate under what conditions to skip a step."