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

171–180 of 536 posts

Re: “It's The Future”

#171

Post by jessaustin »

asimuvPR wrote: post #99
firasd wrote: post #55

Earlier quoted context omitted.

I'm building a podcast discovery app and I find myself being de-facto pulled towards modularity. It's because my feed checker is in Elixir, my site is WordPress-based, and I communicate between them using the WP API, and I'm using Google Cloud SQL, and Elasticsearch on its own virtual machine... The thing is though, the Elixir feed checker has its own database table that tracks whether it's seen an episode in a feed.…

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.

cron jobs

Once these are doing anything other than rotating log files, can the system really be considered monolithic?

Re: “It's The Future”

#172

Post by paradite »

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?

Yes. You are right.

At least you understand the author's intention. I would be worried if some non-technical people took the title literally...

Re: “It's The Future”

#173

Post by asimuvPR »

jessaustin wrote: post #171
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.

cron jobs Once these are doing anything other than rotating log files, can the system really be considered monolithic ?

How do you define a monolith? Please establish that before we discuss further. :)

Re: “It's The Future”

#174

Post by EGreg »

You know what's better than microservices? Nodes. Nodes running open source software that can power a distributed network.

Microservices often hit the same database. You want to be able to split up the database. Not just into shards, but into distributed nodes.

And by doing this, you split up the whole stack.

Re: “It's The Future”

#175

Post by jessaustin »

stepanhruda wrote: post #85
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…

Wait a minute, this sounds familiar. looks at username Oh.

'mrhektor is a green account.

Re: “It's The Future”

#177

Post by sleepyhead »

lambdacomplete wrote: post #52

There are 2 major issues with this: 1) Small teams (~1-5 people) trying to seem "big" by working at Google's scale. 2) Heroku's prices. We are currently (successfully so far) migrating a small Django project from bare Amazon EC2 instances to ECS with Docker. Even using 3 EC2 micro instances (1 vCPU, 1 GB RAM) for the Docker cluster we would spend ~8 USD/month/instance. With Heroku the minimum would be 25 USD/month/dy…

And what is the cost of the working hours spent to migrate to Docker compared to just doing a git push to Heroku?

Re: “It's The Future”

#178

Post by gmfawcett »

vertex-four wrote: post #161
moron4hire wrote: post #152

Earlier quoted context omitted.

That sounds more like your team doesn't know how to use git beyond nothing more than an SVN replacement.

"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?

Re: “It's The Future”

#179

Post by sandGorgon »

imaffett wrote: post #36
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.

i would say for most use cases unless ROI becomes an issue. There is a point of time where it becomes cost effective to run your own S3.

Re: “It's The Future”

#180

Post by allengeorge »

seanhandley wrote: post #42

This needs a "(2015)" adding to the title.

I can always count on at least one comment per tech article with exactly this text.

Having read the article back then (and reread it now) it seems like it's still relevant. Maybe we'll have to add the year qualifier after a while when AWS lambda becomes "the way".

Post reply on HN