Serverless computing on DC/OS with Galactic Fog • Hacker News Board

Re: Serverless computing on DC/OS with Galactic Fog

#11

Post by tobilg » Fri, Jul 22, 2016, 3:43 PM UTC

happyslobro wrote: post #3

How do Mesosphere ops (who are developers first, maybe not so experienced with the operations side) normally manage these services, like Gestalt? How do you keep track of what should be running and how resources should be allocated? Do you just install directly from this service repository, and then update resource allocations as needed, through Marathon or the service itself? Or, do you have a system for managing an…

Also, there's a tool called mesosctl (https://github.com/mesoshq/mesosctl) if you want to start small.

Re: Serverless computing on DC/OS with Galactic Fog

#12

Post by mej10 » Fri, Jul 22, 2016, 4:29 PM UTC

imglorp wrote: post #8

jadbox wrote: post #4

Earlier quoted context omitted.

Isn't the cost significantly higher? Even with bulk pricing, lambda was more than 8x more expensive than ec2 for constant computing.

It depends on your traffic. If you have a million 1ms transactions per second, you'll spend $500k/month, or $6m/year. https://s3.amazonaws.com/lambda-tools/pricing-calculator.htm...

That pricing calculator isn't correct.

From the AWS Lambda pricing page:

    Duration is calculated from the time your code begins
    executing until it returns or otherwise terminates,
    rounded up to the nearest 100ms

So it would really be closed to $1 million per month.

Re: Serverless computing on DC/OS with Galactic Fog

#13

Post by mjb » Fri, Jul 22, 2016, 5:08 PM UTC

philliphaydon wrote: post #7

philliphaydon wrote: post #5

Earlier quoted context omitted.

It's highly dependent on your usage. If you want a crib job to run that isn't on your production server and it's to run every few hours. Great to schedule that on AWS lambda. EC2 would be more expensive. Trying to process 1000s of requests on AWS lambda could end up hitting the limits of lambda and cost you more. I use lambda to process exif data in images as they are uploaded to S3. Which is awesome because it doesn…

Oh and AWS database access sucks balls. Because you cannot pool connections you must open/close db connections. If you fail to close you will exhaust the database connections quickly and kill your app until the connections expire.

Phillip - have you tried making your database connection in 'static' code? With container re-use (see https://aws.amazon.com/blogs/compute/container-reuse-in-lamb...), you should see multiple invokes going to the same container, and you can use the same connection for all of them. That will only happen if your traffic is high enough.

Re: Serverless computing on DC/OS with Galactic Fog

#14

Post by soamv » Fri, Jul 22, 2016, 5:50 PM UTC

markonen wrote: post #2

In my book, the innovation in Lambda is, above everything else, about the billing model. My company moved the work of 40 dedicated servers onto Lambda and in doing so decimated our costs. Paying for 1500 cores (our current AWS limit) in 100ms increments has been a game changer. I'm sure there are upsides to adopting the same programming model with your own hardware or VMs, but the financial benefit of Lambda will not…

There are financial benefits to being able to very easily overcommit resources (although Lambda is just one way to do that).

Re: Serverless computing on DC/OS with Galactic Fog

#15

Post by simonebrunozzi » Fri, Jul 22, 2016, 5:53 PM UTC

markonen wrote: post #2

In my book, the innovation in Lambda is, above everything else, about the billing model. My company moved the work of 40 dedicated servers onto Lambda and in doing so decimated our costs. Paying for 1500 cores (our current AWS limit) in 100ms increments has been a game changer. I'm sure there are upsides to adopting the same programming model with your own hardware or VMs, but the financial benefit of Lambda will not…

That's interesting - it's the first time I read about a 10x cost improvement.

Would you mind sharing a bit more details?

p.s. if you're in the Bay Area I wouldn't mind getting together over coffee/drinks for a deeper chat.

Re: Serverless computing on DC/OS with Galactic Fog

#16

Post by fizzbatter » Fri, Jul 22, 2016, 6:15 PM UTC

I'm very clueless to this new architecture, but a concern i frequently hear about is lockin (both in language and vendor).

Does this style of computing / engineering hinder open source adoption in languages? Eg, OS images pre-setup with some type of PHP-style provider, letting you run whatever language you want with low startup time to handle each request?

I'm sure much of this is way off the mark, so to explain it differently, i'd love to be able to work with a Rust framework tailored to this "serverless" model, and hosted on any generic box i want (or fleets of boxes, etc).

And of course, apologies for the ignorance i'm sure is visible :)

Re: Serverless computing on DC/OS with Galactic Fog

#17

Post by the_arun » Fri, Jul 22, 2016, 7:22 PM UTC

If we want to replace AWS Lambda with self hosted service for Java, what are the recommendations? Apache Mesos ?

Re: Serverless computing on DC/OS with Galactic Fog

#18

Post by k__ » Fri, Jul 22, 2016, 8:49 PM UTC

mjb wrote: post #13

philliphaydon wrote: post #7

Earlier quoted context omitted.

Oh and AWS database access sucks balls. Because you cannot pool connections you must open/close db connections. If you fail to close you will exhaust the database connections quickly and kill your app until the connections expire.

Phillip - have you tried making your database connection in 'static' code? With container re-use (see https://aws.amazon.com/blogs/compute/container-reuse-in-lamb... ), you should see multiple invokes going to the same container, and you can use the same connection for all of them. That will only happen if your traffic is high enough.

I find it kinda strange, that in every official doc they talk about how not to rely on this, but every example I find relies on thsi.

Re: Serverless computing on DC/OS with Galactic Fog

#19

Post by tobilg » Fri, Jul 22, 2016, 9:02 PM UTC

the_arun wrote: post #17

If we want to replace AWS Lambda with self hosted service for Java, what are the recommendations? Apache Mesos ?

Actually, Galactic Fog runs on DC/OS which is at it's core a Mesos distribution. As far as I understood it can't currently run Java lambdas...

Re: Serverless computing on DC/OS with Galactic Fog

#20

Post by luhn » Fri, Jul 22, 2016, 9:03 PM UTC

keithchambers wrote: post #9

markonen wrote: post #2

In my book, the innovation in Lambda is, above everything else, about the billing model. My company moved the work of 40 dedicated servers onto Lambda and in doing so decimated our costs. Paying for 1500 cores (our current AWS limit) in 100ms increments has been a game changer. I'm sure there are upsides to adopting the same programming model with your own hardware or VMs, but the financial benefit of Lambda will not…

There is no disputing the financial model behind AWS Lambda is revolutionary. I know of a visitor NDA signing service that charges $5 per visitor. The backend runs entirely on AWS API Gateway and Lamdba and their cost per visitor transaction to AWS is $0.25. Think about how powerful this is! Now you can develop an app in your spare time and bring it to market for practically nothing. Once developed, your fix infrastr…

I'm struggling to imagine what about an NDA signing service would cost 25c per visitor. 25c buys you ~4 GB-hours in Lambda!