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

Docker Releases Plugin for Simplified Deployments into AWS

infoq.com

Post reply on HN
Print view View original

101–110 of 116 posts

Re: Docker Releases Plugin for Simplified Deployments into AWS

#101

Post by oh_hello »

irjustin wrote: post #7

I am in the process of migrating my stack from Elastic Beanstalk multi-container to Fargate so this looked like an interesting thing I could 'pick up'. This does potentially unify the container definitions between compose and ContainerDefinitions in the task definitions, but for my self, that's not a super helpful tool. Much of the complexity of running Fargate is outside of Fargate, wiring everything up so Route 53…

I also often look at these tools and don't see clearly how they are meant to scale beyond small, isolated projects. The simple examples where you let the tool take your small project and start serving requests from AWS doesn't show me how I would use it in the real world.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#102

Post by leetrout »

SingAlong wrote: post #78
leetrout wrote: post #55

Earlier quoted context omitted.

I’m curious- why ansible instead of terraform for dealing with the cloud provider APIs for your base layer of infrastructure?

TBH because Ansible is what I’ve been using for a long time. And based on what FunnyLookinHat mentions in another comment, Terraform seems to offer a lot less. I have no first-hand experience with Terraform to confirm that.

Yea it’s focused on the infrastructure layer.

It has a separate state mechanism to keep things in sync that Ansible didn’t have the last time I tried only using Ansible. They’re a match made in heaven when put together IMO.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#103

Post by scaryclam »

SingAlong wrote: post #78
leetrout wrote: post #55

Earlier quoted context omitted.

I’m curious- why ansible instead of terraform for dealing with the cloud provider APIs for your base layer of infrastructure?

TBH because Ansible is what I’ve been using for a long time. And based on what FunnyLookinHat mentions in another comment, Terraform seems to offer a lot less. I have no first-hand experience with Terraform to confirm that.

Terraform goes quite a lot further than FunnyLookinHat mentions. I actually don't advocate for using it further than infrastructure myself (I like using specific tooling for specific jobs), but that doesn't mean it can't go a lot further (https://www.terraform.io/docs/providers/index.html for a list of the providers, and it's possible to use the null provider to write some more custom things and hack arounds).

I've had a lot of success coupling Terraform with provisioners like Ansible or Saltstack.

Of course, if Ansible is what you're used to and it works for you, there's no real benefit to using something else right now :) I'm a big fan of Terraform, so I hope you also have a play around with it to see if it can help with what you're doing in the future.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#104

Post by FunnyLookinHat »

nolite wrote: post #74
FunnyLookinHat wrote: post #70

Earlier quoted context omitted.

Terraform is so heavy handed - I wouldn't call it a deployment tool. It's more of a means to build out infrastructure in AWS. Once you get your AWS account setup there's still virtually no tooling to actually manage deploys of new code into that infrastructure. We're going to hand roll some tooling on top of aws-cli most likely.

What's wrong with https://aws.amazon.com/codedeploy/ ?

CodeDeploy is totally fine, but honestly I'm tired of being nickel-and-dimed in AWS.

I'm already paying AWS a massive amount for compute, storage, and bandwidth - I don't want to pay more just be able to use it efficiently.

Maybe it's the FOSS nerd in me - but I can't stand the walled-gardens we're essentially creating in these IaaS providers.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#105

Post by secondcoming »

rubber_duck wrote: post #64
secondcoming wrote: post #57

Earlier quoted context omitted.

It's a totally valid rant, and one that I enthusiastically agree with. I work in adtech (apologies). We have maybe 10 - 15 instances (16 vCPUs, 31GB RAM) that each handle 10k+ HTTP requests per second. There's a push to dockerise all this. I don't see the point. I've often wondered about the potential performance loss of Dockerising all this, do you have public numbers available? We recently hired a ex-Googler to a m…

Well it should be faster if you're replacing the VM layer and running docker on top of bare metal kernels, in theory you could use a cheap dedicated hosting provider to host a K8S cluster and probably outperform a managed cloud offering price and performance wise - but in practice this shit is so unreliable I would never want to be the guy on call maintaining this - they would need to pay me a lot more than the delta…

They wouldn't be bare-metal, they're managed GCE instances

Re: Docker Releases Plugin for Simplified Deployments into AWS

#106

Post by jeremylevy »

qppo wrote: post #100
jeremylevy wrote: post #76

Earlier quoted context omitted.

Thanks! We've released an alpha version, with only one architecture, some days ago. If you want to learn more, I've written a blog post: https://medium.com/revolv2/im-building-revolv-to-automate-cl...

I think your product would work great as an "a la carte" consultancy, it seems well aligned with startups which may have some incentives to pick particular pieces but need help to wire it together - and already need to allocate a developer's salary to do it.

Interesting, thanks!

When you say "'a la carte' consultancy", do you mean with a one-shot payment?

Do you think that the "user-friendly" features (deployment monitoring/rollback, CI on all branches, health monitoring...), that you can't have with Terraform only, are useful enough to ask for a recurring one?

Re: Docker Releases Plugin for Simplified Deployments into AWS

#107

Post by e40 »

cooljacob204 wrote: post #73
b112 wrote: post #47

Earlier quoted context omitted.

The real problem is, people are deploying dozens of different coding languages, any technology that whimsically passes by, and replacing simple, streamlined monolith technology with 100 micro services. All of this is endlessly pushed by AWS, Google, Docker, and anyone else with a foot in the "Snag as much cash from DEVs" crowd. Other old timers will explain how they ran thousands of hits/second on 6 or 7 bare metal s…

You can containerize a monolith server. I think this is more of a microservice issue then a container issue. Docker seriously simplifies my life greatly.

Yes, people do this all the time.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#108

Post by jcims »

scarface74 wrote: post #97
jcims wrote: post #71

Earlier quoted context omitted.

Not the person you are replying too but some industries have regulatory mandates for vendor diversity in cases like this. In addition, when your bills get to millions per month, the provider supplies quite a bit of TAMs and technical resources to your account. This can be helpful, but they also get a good understanding of where you are and are not in a position to dip out if things get sideways in billing. (Also, oth…

When your build gets to be “millions per month”, you are already locked in. Any migrations is going to be a painful multi year progress. “Infrastructure has weight”. Have you been part of an integration with a health care system? They are so tightly locked in to their existing EMR/EHR system it would make you cry. Every third party vendor that comes along has to integrate with it. Part of the work I did at the compan…

You're definitely locked in at some level, but if you are able and even demonstrate the ability to swing 30% of your workload over to another provider in a quarter, you're going to maintain some leverage.

Yes, have worked in healthcare on and off over the past 20 years and know precisely of what you speak. That's a different situation IMHO, same with ERP/HR/etc.

Re: Docker Releases Plugin for Simplified Deployments into AWS

#110

Post by qppo »

jeremylevy wrote: post #106
qppo wrote: post #100

Earlier quoted context omitted.

I think your product would work great as an "a la carte" consultancy, it seems well aligned with startups which may have some incentives to pick particular pieces but need help to wire it together - and already need to allocate a developer's salary to do it.

Interesting, thanks! When you say "'a la carte' consultancy", do you mean with a one-shot payment? Do you think that the "user-friendly" features (deployment monitoring/rollback, CI on all branches, health monitoring...), that you can't have with Terraform only, are useful enough to ask for a recurring one?

What I mean is that early stage startups will have to bootstrap some cloud infra, but their engineering teams are laser focused on creating value for their users and validating product market fit. Every day that a technical founder/early hire spends writing their cloud story is a day taken away from their runway without (directly) creating value that could lead to revenue or funding.

People will pay you to build out their cloud infrastructure one feature at a time, or pick features off the cart as they want them (so maybe like an all you can eat cloud buffet?). There's a bonus to that too, iterative consulting is a great way to validate a tech stack for a problem domain before you figure out how to turn it into a recurring revenue source.

AWS for all its flaws is actually pretty good for this already, which I think is why it gets so popular with seed stage startups before they get locked in (plus the credits that they give out like candy...). I don't have to think about architecture, I google what aws cli command I need to set stuff up and move on with my life.

Post reply on HN