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

61–70 of 536 posts

Re: “It's The Future”

#61

Post by philliphaydon »

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…

Your micro instance has cpu credits while your docter cluster does not? So price increase is expected...

Re: “It's The Future”

#65

Post by nbevans »

jondubois wrote: post #15
nbevans wrote: post #10

Earlier quoted context omitted.

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?

Um no, Rancher is open source can run and manage ANY infrastructure (including Amazon EC2) - You can run it on your own datacenter or even on your own local machine. Also Baasil.io is essentially just a control panel/dashboard (Rancher-as-a-service), you can quit Baasil.io at any time and switch to your own hosted Rancher instance and you don't have to change any of your application code or change infrastructure prov…

I took one look at "baasil.io" and saw the typical landing page with a "Plans" link at the top and questioned why anyone would want to take a dependency on this. If there is some OSS project behind the plan-based charade then that's fine.

"Also Baasil.io is essentially just a control panel/dashboard (Rancher-as-a-service), you can quit Baasil.io at any time and switch to your own hosted Rancher instance and you don't have to change any of your application code or change infrastructure providers."

But so you can with AWS and Azure - especially with their Docker offerings. So I'm not sure what problem baasil.io actually solves? If anything it just adds to the list of dependencies and points of failure.

Re: “It's The Future”

#66

Post by buro9 »

forgottenacc56 wrote: post #34
Svenskunganka wrote: post #28

Earlier quoted context omitted.

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.

Plus visitors != requests.

I have 200k visitors per month generating 8m page views and about 50m hits on the servers (with CDNs taking another few hundred million hits).

These all peak during the UK weekdays and wind down at nights and weekends.

Divisions over time aren't going to work, but neither is translating visitors into requests, especially as it's only the page views that have a beyond trivial computation cost.

Re: “It's The Future”

#67

Post by notimetorelax »

buro9 wrote: post #54
mrweasel wrote: post #50

Earlier quoted context omitted.

>Any positive experiences with micro-services here? It makes sense for some thing. We run a webshop, but have a separate service that handles everything regarding payments. It has worked out really well, because it allows us to fiddle around with pretty much everything else and not worry about breaking the payment part. It helps that it's system where we can have just one test deployment and everyone just uses that d…

> have a separate service that handles everything regarding payments. It has worked out really well, because it allows us to fiddle around with pretty much everything else and not worry about breaking the payment part. Is the payments service a single service that manages the whole transaction, or have you go for multiple services handling each part and, if so, how did you manage failure with a distributed transactio…

Not sure if it's the case here. But what works really well for us is queues with at-least-once guarantee. (For payment services you might need an additional check to guarantee exactly one execution.) I think you can find this queue offered by most providers.

Re: “It's The Future”

#68

Post by elsurudo »

forgottenacc56 wrote: post #34
Svenskunganka wrote: post #28

Earlier quoted context omitted.

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.

While you overall point is correct, it's still likely not going to be a lot. It's highly unlikely that it's 40k per second.

Re: “It's The Future”

#69

Post by nickjj »

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.

Re: “It's The Future”

#70

Post by axelfontaine »

djhworld wrote: post #11

One thing that I liked about Heroku was the ease of deployment for Java applications (or any language for that matter as long as you had the right build pack) Since they upped the cost of their small tier, I moved to Digital Ocean and installed Dokku, which gives me that Heroku-like deployment experience so managing my (admittedly very small) website isn't that much of a hassle.

We at Boxfuse (https://boxfuse.com) provide the same ease of deployment for running Java apps (as well as Go and Node.js ones) on AWS. All you need to type is literally: boxfuse run myapp-1.0.jar -env=prod

And you automatically get things like auto-scaling, database auto-provisioning. easy debugging and more.

Disclaimer: I'm Boxfuse's founder and CEO

Post reply on HN