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

181–190 of 536 posts

Re: “It's The Future”

#181

Post by collyw »

firasd wrote: post #110
asimuvPR wrote: post #99

Earlier quoted context omitted.

I think your problem might be not expanding wordpress. PHP will gladly do the above through wordpress plugins and cron jobs. I built something similar and ended up going that way. The system is still running to this day. Sure, its not hip but gets the job done with miniml fuss and makes money.

You are right that PHP can do the feed checking part but I wanted to use something with easy async/concurrency out of the box (and wanted to learn Elixir instead of using Node.) One hard tech limit is that with 50k podcasts, 4million+ episodes, search definitely doesn't work well. Not just WP, but SQL itself. Hence Elasticsearch. I also plan to work on recommendations, etc. so will need probably to be exporting SQL d…

I generally write what I consider monolithic Django apps. I would add in Haystack (a search module for Django) and configure it to use Elasticsearch to overcome the problems you describe.

It doesn't sound like microservices are needed, just adding in the appropriate tech for the job.

Re: “It's The Future”

#182

Post by sandGorgon »

nickjj wrote: post #69
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,…

Once you finish taking my Scaling Docker on AWS course, you'll have access to a magic command that deploys your app and you're free to optionally run migrations. http://nickjanetakis.com/courses/scaling-docker-on-aws It covers using RDS, ElastiCache and also handles load balancing your app + much more.

i have grappled with Amazon ECS and im in no mood to go through that again. Convox (YC S15) is a pretty good alternative - but it will take some time for them to tie the "magic" together.

Re: “It's The Future”

#184

Post by sandGorgon »

jeremyjh wrote: post #49
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,…

Deis will do exactly that. http://deis.io/

hey - not bad. The documentation looks very similar to heroku.. i cant find if they do stuff to handle workers in Procfiles (which need to be added to the job manager like supervisord/systemd). But interesting..

Re: “It's The Future”

#185

Post by DasIch »

chukye wrote: post #111

Man, I dont think this is the future at all. OK, Docker is good and has its propose, and is very good on what its do: "Run only one process in one brand new kernel", but beyond than that, its just a daemon that uses and abuses of linux containers, you can easily scale, but is a pain in the ass to upgrade apps, also you need to run only one process on that. Does not looks like the future for me to have 30 different li…

It comes down to not wanting different applications (not equivalent to processes) to share a single filesystem and all that implies like shared dependencies.

Re: “It's The Future”

#186

Post by IshKebab »

piva00 wrote: post #170
chukye wrote: post #111

Man, I dont think this is the future at all. OK, Docker is good and has its propose, and is very good on what its do: "Run only one process in one brand new kernel", but beyond than that, its just a daemon that uses and abuses of linux containers, you can easily scale, but is a pain in the ass to upgrade apps, also you need to run only one process on that. Does not looks like the future for me to have 30 different li…

It's all about simplifying deployment. That's it, that's what's so good about using containers. I don't know if you understand what Docker really is when you say something like this: "Run only one process in one brand new kernel", the kernel is shared between containers, that's the whole idea, you package the things your application need and be done with it. The current problem with containerization is that there are…

Doesn't statically compiling programs solve the deployment issue better? I mean, as far as I can tell Docker only exists because it's impossible to link to glibc statically, so it's virtually impossible to make Linux binaries that are even vaguely portable.

Except now Go and Rust make it very easy to compile static Linux binaries that don't depend on glibc, and even cross-compile them easily.

Hell I think it's actually not even that hard to do with C/C++: https://www.musl-libc.org/how.html

If I have a binary built by Go, what problems does Docker solve that just copying that binary to a normal machine doesn't?

Re: “It's The Future”

#188

Post by prima-facie »

dirtyhenry wrote: post #168
rajeshp1986 wrote: post #109

The article perfectly summarizes my frustration and sentiment. These days I hear these buzzwords all time. I work as a consultant for an enterprise product and most people whom I meet they somehow catch these buzzwords and blurt it out in front of everyone during meetings and discussions to either showoff that they know technology and things that are in the market these days(also latest iphone, apple news, tesla, spa…

Totally agreed. As a freelance, it's really scary to invest time into a full stack of technologies. I should start a discipline to pick tools and not look back before n years went by. Maybe n = 2 or 3 ? (right now, I'm Objective-C - not even Swift - for native iOS, Ember for client, Rails for API/back-office and Heroku for deployment)

Swift should be mature enough by now for development. Or start with version 3 when it comes out.

Re: “It's The Future”

#189

Post by Xylakant »

gmfawcett wrote: post #178
vertex-four wrote: post #161

Earlier quoted context omitted.

"We rolled out this update with 220 changes. There's a breaking bug. Where is it? We need to find out in the next 5 minutes, revert, and deploy. Otherwise we have to revert the whole thing- we're losing money." Git doesn't really help with that. More granular deployments do, and if microservices help with more granular deployments, go for it.

Git-bisect does, doesn't it?

Only if you have a test that catches the bug and it still needs time to run. You'll also need time to write a fix, validate it and deploy. Plus any extra time your organization needs between code and deployment

Re: “It's The Future”

#190

Post by hacksonx »

hellofunk wrote: post #18

I assume this entire article is one piece of sarcasm. Because after reading it, how could any sane person not prefer Heroku?

Read it and passed it around to the guys at the office and I can tell you that it goes beyond the Heroku v Docker debate. For us, here at some kind of bank development shop it is about languages and frameworks. I would advice that you read the whole thing. Pretty funny I must add.
Post reply on HN