Live data from Hacker News

Carina – High-Performance, Instant-On Docker Containers

getcarina.com

1–10 of 37 posts

Re: Carina – High-Performance, Instant-On Docker Containers

#3

At first glance this looks incredible but what's with the naming of a "segment" ???

This is a concept that doesn't even exist in most other systems, so there isn't an agreed name for it (we call it a "slice" in Spyre). It's similar to a Kubernetes "pod" but not quite.

Re: Carina – High-Performance, Instant-On Docker Containers

#4
post #3

At first glance this looks incredible but what's with the naming of a "segment" ???

This is a concept that doesn't even exist in most other systems, so there isn't an agreed name for it (we call it a "slice" in Spyre). It's similar to a Kubernetes "pod" but not quite.

Exactly - we really struggled with this. A node (for example, when doing a Docker info when having $SWARM hosts) implies to the user physical isolation. As a distributed systems nerd, I pushed for "anything that doesn't make a contract it's on a different machine". Segment, slice, pod, chunk, block - something other than implying the isolation and therefore fault tolerance of the overall system.

https://getcarina.com/docs/faq/ has more

Re: Carina – High-Performance, Instant-On Docker Containers

#6
People using stupid captioned images in their blog posts and technical announcements are a real turn off for me; I'm not sure if people are trying to be funny or edgy but it comes off really lame and childish. Feels like being in one of the Reddit default subs.

Re: Carina – High-Performance, Instant-On Docker Containers

#7
post #6

People using stupid captioned images in their blog posts and technical announcements are a real turn off for me; I'm not sure if people are trying to be funny or edgy but it comes off really lame and childish. Feels like being in one of the Reddit default subs.

Eh, the corporate world is bland and grey. I'm glad if a company does something different.

Re: Carina – High-Performance, Instant-On Docker Containers

#8
post #4
post #3

Earlier quoted context omitted.

This is a concept that doesn't even exist in most other systems, so there isn't an agreed name for it (we call it a "slice" in Spyre). It's similar to a Kubernetes "pod" but not quite.

Exactly - we really struggled with this. A node (for example, when doing a Docker info when having $SWARM hosts) implies to the user physical isolation. As a distributed systems nerd, I pushed for "anything that doesn't make a contract it's on a different machine". Segment, slice, pod, chunk, block - something other than implying the isolation and therefore fault tolerance of the overall system. https://getcarina.com…

This level abstraction seems unnecessary. We need to just let-go of the concept of physical or virtual hosts. A machine should boot and join a cluster, advertising its capabilities (ssd drives, gpu's, enhanced networking, it's availability zone or region, etc...) and you should never need to think about that stuff, period.

I don't care how many devices/segments/nodes/slices/dynos/widgets are in my cluster. I care that I have X GB of total memory and Y cpu's. I want to check a box to make an app or service highly available (on more than one node, and in more than one zone) and Ronco™ set it and forget it.

Everything else is just noise.

I love the ideas behind Kubernetes and Fleet/CoreOS (and this) but everyone is SO excited about these low level technologies that have yet to be composed into beautiful experiences.

A tweet from Kelsey Hightower sums it up perfectly:

    It's going to be nearly impossible for people
    to evaluate and chose a container management platform
    during the gold rush.
https://twitter.com/kelseyhightower/status/65918202241030553...
Post reply on HN