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

“It's The Future”

circleci.com

Post reply on HN
Print view View original

31–40 of 536 posts

Re: “It's The Future”

#31

Post by mrhektor »

"-No, look into microservices. It’s the future. It’s how we do everything now. You take your monolithic app and you split it into like 12 services. One for each job you do.

That seems excessive"

A 100 times yes. We tried to split our monolithic Rails app into micro-services built in Go. 2 years and many fires later, we decided to abandon the project. It was mostly because the monitoring and alerting were now split into many different pieces. Also, the team spent too much time debating standards etc. I think micro-services can be valuable, but we definitely didn't do it right, and I think a lot of companies get it wrong. Any positive experiences with micro-services here?

Re: “It's The Future”

#32

Post by reitanqild »

Pyxl101 wrote: post #16
forgottenacc56 wrote: post #7

Earlier quoted context omitted.

I'm sure I don't get that message.

It's all sarcastic. It's poking fun at how trendy advances might not necessarily be better than what existed before, as well as how much complexity is involved in them. It makes the most sense if you're already familiar with the concepts in the article (Docker, Heroku, CoreOS, etcd, and so on), and happenings in the technology industry related to them. As usual, if a joke needs to be explained (to a person) then it's…

I learned that will laugh at a joke three times:

* First when you tell it,

* then when you explain it,

* then finally when they get it.

(x used to be English people when I was a kid.)

Re: “It's The Future”

#33

Post by LoSboccacc »

nbevans wrote: post #10
jondubois wrote: post #9

That's why we started https://baasil.io/ . The idea is you can deploy any app to any infrastructure of your choice (inside Docker containers). This means that you are not locked into Heroku and it gives you much more flexibility. It's basically a hosted Rancher http://rancher.com/ service with a focus on a specific stack. I think in the future, there will be a lot of services like Baasil.io (specializing in various s…

But all you've done is shift the problem to, er, you. If someone is uncomfortable taking out a dependency on say Azure or AWS - the two leading Docker hosting platforms, then they sure as hell aren't going to take out a dependency on "baasil.io" are they?

xkctext: we saw 15 competing standard, so we decided to invent our standard that encompass all the previous one!

Re: “It's The Future”

#34

Post by forgottenacc56 »

Svenskunganka wrote: post #28
joeblau wrote: post #21

https://www.gitignore.io runs on Heroku and it gets 40k+ visitors a month on a free Dyno. I use Heroku because I don't want an IAAS solution, I want a PAAS solution. If I wasn't using Heroku, I would probably find another PAAS, before switching to Docker (even though I do love Docker).

That's 1 request per minute, you could slap that into a raspberry pi on a 3G connection, and do the same for your next 400 apps that has 1 request per minute. People seem to underestimate just how powerful modern machines really are. And I don't get why people seem to think it's hard to deploy simple web applications. Just write a 4-line shell script that rsync's, runs whatever DB migrations you may have and restarts…

40k visitors per month isn't one per minute. It's anywhere from one per minute to 40k per second. Division of requests by time is the worst possible mistake in calculating load.

Re: “It's The Future”

#35

Post by nicolas_t »

Out of topic but, man, is coreos not ready for prime time. I've been using it following the stable channel and ended up having to turn off automated updates because it would break docker (docker would just hang with the last 4 updates)... Not a very convincing test of coreos :)

Re: “It's The Future”

#36

Post by imaffett »

sandGorgon wrote: post #14

show me an easy way to push a rails application to aws (with docker) that uses RDS ? is there ANY way i can spin up a server, add the ssh keys to some configuration file somewhere and just "docker-magic push" and have my rails application running ? or do "docker-magic bundle exec db:migrate" and have that command run on the server. Or push a Procfile with worker definitions and have the PAAS automatically pick it up,…

Ive been looking for the same thing. Tried dokku and it was painfully slow. Tried rolling my own solution via git hooks but other devs had problems with execution. I would love to hear more about people running dokku on Digital Ocean (I was on a beefy azure server)

In a very specific case, Heroku is the best solution for my problem. Sounds like it is for you too.

Re: “It's The Future”

#39

Post by forgottenacc56 »

mrhektor wrote: post #31

"-No, look into microservices. It’s the future. It’s how we do everything now. You take your monolithic app and you split it into like 12 services. One for each job you do. That seems excessive" A 100 times yes. We tried to split our monolithic Rails app into micro-services built in Go. 2 years and many fires later, we decided to abandon the project. It was mostly because the monitoring and alerting were now split in…

What was the benefit you envisioned?

Re: “It's The Future”

#40

Post by jondubois »

Kubernetes/Docker will become increasingly accessible to developers and it will loosen the reliance on lock-in PaaS like Heroku - This is the future; I'm betting everything on it.

With tools like Rancher http://rancher.com, you can already see things moving in that direction. Next step is rancher-as-a-service.

When it comes to developers, I think open systems will always prevail in the end (it's just more flexible).

Post reply on HN