Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Carina – High-Performance, Instant-On Docker Containers

getcarina.com

Post reply on HN
Print view View original

31–37 of 37 posts

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

#31

Post by jnoller »

IanCal wrote: post #27
nzoschke wrote: post #24

Earlier quoted context omitted.

Containers are here to stay and almost certainly will be the new abstraction of computation. My big question is around a service like AWS Lambda. Is that not already the logical conclusion of container based computation? If magic units of computation can run instantly on demand, what more do you need? No hosts, but also no OS images, and no specific containerization tools!

It's a massive shame that PiCloud went down as that had containerized environments, extremely fast startups and auto scaling. It was one of the few things I've used that really solved my small-scale data processing problems simply and cheaply. > If magic units of computation can run instantly on demand, what more do you need? Some control over flow, scaling and batching wrap everything up for me. Startup times for my…

We rebuilt picloud as a foray into the getcarina.com space - https://github.com/cloudpipe/cloudpipe we're going to be bringing that back now that carina is landed.

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

#33

Post by nzoschke »

abrookewood wrote: post #29
nzoschke wrote: post #23

Earlier quoted context omitted.

I'm not disappointed. It's great to see Rackspace competing in container services. But I agree... At this level of abstraction ECS is far more attractive because of the rest of the AWS services and ecosystem. Joyent deserves a lot of credit for removing the extra layer. However Triton is missing key functionality like a good load balancer. Abstractions are important, but pure functionality is more important. How can…

Can you link to that review please? Triton sounds very interesting.

Sure! In summary Triton is really awesome but it needs a load balancing service for starters...

http://stackshare.io/convox/amazon-ecs-vs-joyent-triton

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

#34

Post by phymata »

callahad wrote: post #5

This looks fun. Any word on ballpark pricing or the duration of the beta? (or at least a lower bound on anticipated pricing -- will there be plans that are suitable for hobbyists who are otherwise on DO's $5-10/mo tier.)

https://getcarina.com/docs/faq#how-long-will-carina-be-free-...

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

#35

Post by abrookewood »

nzoschke wrote: post #33
abrookewood wrote: post #29

Earlier quoted context omitted.

Can you link to that review please? Triton sounds very interesting.

Sure! In summary Triton is really awesome but it needs a load balancing service for starters... http://stackshare.io/convox/amazon-ecs-vs-joyent-triton

Excellent article - thanks. If you do a follow up, I'd love to see some performance comparison between the two approaches.

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

#36

Post by DannoHung »

pbowyer wrote: post #25
DannoHung wrote: post #19

Earlier quoted context omitted.

Your assessment is accurate, unfortunately Triton does not address the issue of data locality, which is a pretty big problem unless you're already building your storage backend to be Smart Data Center aware. To that extent, I'm not sure that tossing out the idea of hosts is great yet.

> Triton does not address the issue of data locality, which is a pretty big problem unless you're already building your storage backend to be Smart Data Center aware. Can you expand on this please? I was not aware of the problem.

To put it as simply as possible: Triton does not have magic block storage. If you want to write anything that persists past a container's lifetime, it is tied to the machine instance the container was running on unless you manually move it around.

It's not any worse than you'd have if you were starting from scratch with your own hardware, but Bryan Cantrill is firmly against magic block storage. His suggestion is that you rewrite your persistence layer to know about SDC or "deal with it".

It's not necessarily that bad since a lot of containers don't need state, but my personal axe is that I work with databases almost exclusively.

Post reply on HN