Samsung Acquires Joyent • Hacker News Board

Re: Samsung Acquires Joyent

#181

Post by [deleted] » Thu, Jun 16, 2016, 2:23 PM UTC

bkanber wrote: post #160

urza wrote: post #155

Cloud orchestration, Container Orchestration, Kubernetes... I think I am getting old and starting to understand how my parents feel about technology. I am developer, but mostly work on desktop apps, or embedded devices or lataly on some MVC applications. But reading things like "A Container-Native Stack for Modern Applications and Operations Increase development velocity while simplifying operations." I have no idea…

So, you build a web app and it gets popular. It needs one load balancer, 5 app servers, at least two database nodes for replication, a redis cluster for caching and queuing, an elasticsearch cluster for full text search, and a cluster of job worker servers to do async stuff like processing images, etc. In the ancient past, like when I'm from, you'd write up a few different bash scripts to help you provision each serv…

[deleted]

Re: Samsung Acquires Joyent

#182

Post by cloakandswagger » Thu, Jun 16, 2016, 2:25 PM UTC

markatkinson wrote: post #177

Raphmedia wrote: post #175

Earlier quoted context omitted.

We need a HN Best-of comment section and we need to put your comment into it.

You could start a whole separate website of just "Best HN comments".

There's no need for a separate website, HN already provides a collection of best comments:

https://news.ycombinator.com/threads?id=cloakandswagger

Re: Samsung Acquires Joyent

#183

Post by urza » Thu, Jun 16, 2016, 2:29 PM UTC

bkanber wrote: post #160

urza wrote: post #155

Cloud orchestration, Container Orchestration, Kubernetes... I think I am getting old and starting to understand how my parents feel about technology. I am developer, but mostly work on desktop apps, or embedded devices or lataly on some MVC applications. But reading things like "A Container-Native Stack for Modern Applications and Operations Increase development velocity while simplifying operations." I have no idea…

So, you build a web app and it gets popular. It needs one load balancer, 5 app servers, at least two database nodes for replication, a redis cluster for caching and queuing, an elasticsearch cluster for full text search, and a cluster of job worker servers to do async stuff like processing images, etc. In the ancient past, like when I'm from, you'd write up a few different bash scripts to help you provision each serv…

Wau thanks, that is an excellent explanation. I appreciate that it start with things I know and understand ("so you build a web app"/"bash scripts"/"puppet") and builds on that explaining what problems each consecutive steps /layer of abstraction/ solves.

Now I wonder.. how many projects actually needs these kind of solution when even StackOverflow can do without it (they are in the range of few servers)? I would imagine it would be only few top popular web apps/services, but by popularity of these posts it looks like it is probably a lot more...

Re: Samsung Acquires Joyent

#184

Post by planteen » Thu, Jun 16, 2016, 2:31 PM UTC

cloakandswagger wrote: post #182

markatkinson wrote: post #177

Earlier quoted context omitted.

You could start a whole separate website of just "Best HN comments".

There's no need for a separate website, HN already provides a collection of best comments: https://news.ycombinator.com/threads?id=cloakandswagger

I see what you did there

Re: Samsung Acquires Joyent

#185

Post by mschuster91 » Thu, Jun 16, 2016, 2:34 PM UTC

bkanber wrote: post #160

urza wrote: post #155

Cloud orchestration, Container Orchestration, Kubernetes... I think I am getting old and starting to understand how my parents feel about technology. I am developer, but mostly work on desktop apps, or embedded devices or lataly on some MVC applications. But reading things like "A Container-Native Stack for Modern Applications and Operations Increase development velocity while simplifying operations." I have no idea…

So, you build a web app and it gets popular. It needs one load balancer, 5 app servers, at least two database nodes for replication, a redis cluster for caching and queuing, an elasticsearch cluster for full text search, and a cluster of job worker servers to do async stuff like processing images, etc. In the ancient past, like when I'm from, you'd write up a few different bash scripts to help you provision each serv…

> All the apt-get install crap was done at image build time, not container launch time.

Something I never understood with containers: where do they store persistent data, e.g. MySQL's /var/lib/mysql - and how does upgrading work, i.e. when the apt-get postinstall script runs transformation on the persistent data, how is the transformation applied to the "clones"?

Re: Samsung Acquires Joyent

#186

Post by bkanber » Thu, Jun 16, 2016, 2:37 PM UTC

urza wrote: post #183

bkanber wrote: post #160

Earlier quoted context omitted.

So, you build a web app and it gets popular. It needs one load balancer, 5 app servers, at least two database nodes for replication, a redis cluster for caching and queuing, an elasticsearch cluster for full text search, and a cluster of job worker servers to do async stuff like processing images, etc. In the ancient past, like when I'm from, you'd write up a few different bash scripts to help you provision each serv…

Wau thanks, that is an excellent explanation. I appreciate that it start with things I know and understand ("so you build a web app"/"bash scripts"/"puppet") and builds on that explaining what problems each consecutive steps /layer of abstraction/ solves. Now I wonder.. how many projects actually needs these kind of solution when even StackOverflow can do without it (they are in the range of few servers)? I would ima…

How many people actually need it? Nobody! We managed to run servers for years without containers or orchestration tools. Docker is a new technology.

Does it make things better, though? Yes. Yes it does.

Kubernetes was designed at Google where they reaaaaally feel their scale problems day to day.

I see Docker/Kube/CoreOS/ etc as the natural evolution of where we were already going. Bash -> puppet -> vagrant -> docker -> kubernetes. Less abstract to more abstract.

So it's actually "only" an incremental evolution in terms of managing the server ecosystem. But it's a revolutionary improvement in how we think about server ecosystems, which is why many people struggle with Docker et al at first; it's a brand new mental model.

Re: Samsung Acquires Joyent

#187

Post by ethbro » Thu, Jun 16, 2016, 2:38 PM UTC

smt88 wrote: post #31

ethbro wrote: post #2

So this is the moment where everyone with a sufficient device / install marketshare decides they need to buy cloud expertise? "Samsung will immediately benefit from having direct access to Joyent’s technology, leadership and talent. Likewise, Joyent will be able to take advantage of Samsung’s scale of business, global footprint, financial muscle and its brand power."

Samsung is (and has been) terrified that their handset business will be slaughtered in the race to the bottom of the hardware industry. They tried to create their own OS to give themselves an edge over other Android manufacturers. Their fears have come true (and now it's even happening to Apple). Hardware is an incredibly difficult, risky business, and differentiation is now in the services/software arena. That's why…

One thing that I never understood was how the Android hardware ecosystem never saw contributing resources to developing more efficiently abstracted core Linux + Android support for their hardware compatibility challenges as a competitive advantage.

Disclaimer: I'm not involved in that space, so maybe they've started?

Re: Samsung Acquires Joyent

#188

Post by dragonwriter » Thu, Jun 16, 2016, 2:46 PM UTC

tokenizerrr wrote: post #108

vertex-four wrote: post #105

Earlier quoted context omitted.

Linux has a specific amendment to the GPLv2 stating that it must always be distributed under the terms of the GPLv2, not the GPLv3 or any later version.

Honest question, how is anyone expected to keep up with all of this? Software licenses are not all that interesting to me, I just like making things, but now I have to also read pages and pages of legalize for every single dependency. I thought it would be good enough to know most mainstream licenses, but apparently Linux has a modified version of the GPLv2? I would never notice that, nor would I trust myself to even…

It's not a modified GPLv2; the "or any later version" allowance in the GPL is optional (see clause 7 of GPLv1, clause 9 of v2, and clause 14 of v3.)

So, if you "know must mainstream licenses", you should be aware of this.

Re: Samsung Acquires Joyent

#189

Post by bkanber » Thu, Jun 16, 2016, 2:46 PM UTC

mschuster91 wrote: post #185

bkanber wrote: post #160

Earlier quoted context omitted.

So, you build a web app and it gets popular. It needs one load balancer, 5 app servers, at least two database nodes for replication, a redis cluster for caching and queuing, an elasticsearch cluster for full text search, and a cluster of job worker servers to do async stuff like processing images, etc. In the ancient past, like when I'm from, you'd write up a few different bash scripts to help you provision each serv…

> All the apt-get install crap was done at image build time, not container launch time. Something I never understood with containers: where do they store persistent data, e.g. MySQL's /var/lib/mysql - and how does upgrading work, i.e. when the apt-get postinstall script runs transformation on the persistent data, how is the transformation applied to the "clones"?

"Volumes" are the Docker construct used to store persisted data. You use a volume when you want to decouple the lifecycle of your data with the lifecycle of the app. You can either map the volume to a directory on the host (ie, map /var/lib/mysql to ~/data/mysql), or you can allow Docker to manage it (where it'll live in /var/lib/docker/volumes/blah/blah).

You don't upgrade a running container. Imagine that containers are immutable; to launch a new, upgraded version, you re-build the image in your build/dev environment, and re-launch the image into production. If you're using a volume, you get to use the same backing data.

It's rare that apt-get postinstall will affect any data that you would persist -- app-specific data you'd keep in the image/container, and mysql data for instance you don't really want apt touching anyway. But if a data migration is necessary you'd either manage it with a "utility container" (image that's designed to run a script then stop, rather than run and keep running).

Re: Samsung Acquires Joyent

#190

Post by ci5er » Thu, Jun 16, 2016, 2:55 PM UTC

hitr wrote: post #15

I always thought Microsoft/Google or the likes would acquire Joyent as it is good product fit. Microsoft chose linkedin instead :) For Samsung this is all about IoT .Samsung wants to own both the devices and backend. A good move IMHO

As Microsoft becomes the new IBM, except for XBox, their future revenue is firmly from the Global 10000 Enterprise space. LinkedIn gives them the entire database (up to date! SF.com doesn't give you that!) of decision makers in their target market and their web of professional relationships.