Matt,
Yes, indeed, we do have the Definition. The TOC worked on this along
with the layered stack (architecture) and landscape (which fits into
the stack). You are 100% right that there should be greater clarity
and consistency. Without this we get confusion and worse. So, the
CNCF TOC should regularly review *all* core technical content with
those criteria in mind. There was an Architecture WG for this, which
could be revived in some form. I think this could help in lots of
ways, including the arduous job of marketing CNCF.
alexis
toggle quoted message
Show quoted text
On Fri, Jun 7, 2019 at 6:59 PM Matthew Farina <matt@...> wrote:
Alexis,
Maybe you can help me with this. The CNCF has a Cloud Native definition. A lot of things fit this bill in one way, shape, or form. Far more than are in the landscape. What is missing that the landscape should account for and why?
If something stricter is to be used it needs to be clearly documented and consistently applied. This allows for things to be fair and to keep it outside the realm of tribal knowledge.
--
Matt Farina
mattfarina.com
On Jun 7, 2019, at 1:35 PM, Alexis Richardson <alexis@...> wrote:
Matt
OK, but:
We are doing a disservice to new users by publishing a "cloud native"
landscape, that contains non-cloud-native projects. If we don't have
an opinion about what is cloud native and what is not, then what is
our purpose?
Other than I fully agree with you.
a
On Fri, Jun 7, 2019 at 6:01 PM Matthew Farina <matt@...> wrote:
When we first made the landscape, it (1) had a particular structure
and (2) attempted to show what projects are cloud native and where
they live in that structure.
Now, it has everything in it. So it is meaningless.
I have to respectfully disagree that it’s meaningless.
Consider the case where someone is new to the space or a category in it. Where does one start to find the options in the space? Search engines are pretty limiting. Especially since this packed space has more than 10 options in each area.
New people to the space should be a high priority because there are more people we would like to come into the space than are already here today. I find the landscape helps them discover what’s in the space. It’s an onboarding tool. We need more of those.
Of course there are questions about netdata. Is netdata a competitor to Prometheus? As an outside observer, it looks like it can monitory lots of things including containers. With Prometheus I can monitory containers, microservices, and even VMs. Again, this is just me as an external observer.
Should people be able to discover the monitoring tools that can monitor containers in the landscape? That’s the question I would look at. Or, is there some other criteria? If so, it would be worth sharing so it’s not tribal knowledge locked in the minds of a few people.
--
Matt Farina
mattfarina.com
