+1 Sent from my Verizon, Samsung Galaxy smartphone

+1 Alexis Richardson via cncf-toc <cncf-toc@...> schrieb am Mi., 15. Feb. 2017, 18:11:

MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_117623181166990" ----_com.samsung.android.email_117623181166990 Content-Type: text/plain;

+1

Hey CNCF TOC community, it's time to vote on the gRPC (http://www.grpc.io/) proposal as an inception level project, you can view the proposal below in this email or on

CNCF TOC Community, Reminder that the TOC will be meeting on Wednesday, February 15, from 3:40pm - 5:10pm PT sharp. Dial-in: https://www.uberconference.com/cloudnative or +1-415-579-0198 No PIN For

Dynamic, or horizontal.... -- Scott McCarty, RHCA Technical Product Marketing: Containers Email: smccarty@... Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com When

Andy, I like dynamically scalable. That's much better. I'd also like to add that what we're proposing here is that people can get any or all of those 3 by going cloud native. I think that's an

<cncf-toc@...> wrote: Agreed. I can only remember about 3 of the 12-factors :-)

I think we should aim for 3 core principles. Any more than that and people won't be able to repeat as a mantra. Currently the charter has: - container packaged - dynamically managed - micro-services

I agree that we may need to think more about how we communicate about microservices, but do we agree that the underlying purpose of cloud native is: 1. Speed of change (I used to refer to this as

Microservices are cloud native because they are a natural product of the ease of use for cloud. In a evolutionary way I would call them absolutely cloud native, which doesn't mean one must use them to

Yes, I don't think microservices is a core value. It's one of several modern cloud native patterns that is useful for some organisational and technical issues. But not the only one.

I'd argue that if you had good tools, you wouldn't need microservices.

Mark, Those are good too :-) Please see my reply to Dustin. Can we come up with "5 values"? (or is it 3? it can't be more than 5). What are the key freedoms and capabilities that impact cloud

I like those Dustin. Can we come up with "5 values"? Let's say that Sally is a developer, and thinking about attending a Cloud Native conference or meetup in 2017. What are the shared values of the

*but obviously = *because obviously -- +31 652134960 CEO www.implicit-explicit.com Co-Founder www.softwarecircus.io Marketing Chair www.cncf.io

I think I summarised it in this piece that I ghost wrote for Luke when he was at ClusterHQ (Friend D A please): https://www.infoq.com/articles/microservices-revolution We have a cloud native triangle

<cncf-toc@...> wrote: +1 to those. Here are a few others: - interoperability with others - choice/plugability at every level - velocity, but stability

yes we need to develop a cloud native brand that has values which developers want - free & open - automated pipelines - faster to make changes - ..?