In The Works – Amazon Aurora Serverless • Hacker News Board

Re: In The Works – Amazon Aurora Serverless

#11

Post by strong_silent_t » Wed, Nov 29, 2017, 5:07 PM UTC

drej wrote: post #2

Cool... but.. how?

So, if I'm understanding right, it is using the database server instances as the current Aurora does. You just aren't responsible for managing them, the service makes those decisions within the spectrum of Aurora's capabilities and can change it in a very small time increment.

EDIT: pretty impressive though, looking at James Hamilton's criteria for "Automatic Management and Provisioning" here: https://www.usenix.org/legacy/event/lisa07/tech/full_papers/... , I think this addresses everything database related, as long as you are under the maximum capacity of Aurora.

Re: In The Works – Amazon Aurora Serverless

#12

Post by ignoramous » Wed, Nov 29, 2017, 5:23 PM UTC

brootstrap wrote: post #3

3 months later... AWS announces serverless, databaseless database system.

Which might be when their marketing team decides to re-launch S3?

Re: In The Works – Amazon Aurora Serverless

#13

Post by mrep » Wed, Nov 29, 2017, 5:31 PM UTC

Is this for the master or the read replicas?

If it is for the master, that would be amazing and I would wonder if you can scale up past the 1 instance size max (currently r4.16xl)

Re: In The Works – Amazon Aurora Serverless

#14

Post by maxxxxx » Wed, Nov 29, 2017, 5:32 PM UTC

brootstrap wrote: post #3

3 months later... AWS announces serverless, databaseless database system.

And then "cloudless"?

Re: In The Works – Amazon Aurora Serverless

#15

Post by k__ » Wed, Nov 29, 2017, 5:35 PM UTC

sologoub wrote: post #10

Really wish "serverless" also meant that it can work with AWS Lambda efficiently. As is, each function would try to open a connection, making the overall overhead extremely high and stressing DBs.

Can't you open the connection outside of the function?

So as long as the function is hot, it won't reconnect.

Re: In The Works – Amazon Aurora Serverless

#16

Post by nleach » Wed, Nov 29, 2017, 5:50 PM UTC

sologoub wrote: post #10

Really wish "serverless" also meant that it can work with AWS Lambda efficiently. As is, each function would try to open a connection, making the overall overhead extremely high and stressing DBs.

Is that true? The default limit on concurrent function executions is 1000. The existing Aurora (MySQL) should be able to handle cycling through those connections without issue.

Re: In The Works – Amazon Aurora Serverless

#17

Post by mjb » Wed, Nov 29, 2017, 5:55 PM UTC

k__ wrote: post #15

sologoub wrote: post #10

Really wish "serverless" also meant that it can work with AWS Lambda efficiently. As is, each function would try to open a connection, making the overall overhead extremely high and stressing DBs.

Can't you open the connection outside of the function? So as long as the function is hot, it won't reconnect.

That's right. Make connections to databases (and most other things) the first time your Lambda handler runs, and stash them in a static/global variable for re-use on future runs. That allows you to amortize the cost of forming the connection over many executions of your function, which improves latency, reduces cost, and reduces load on the backend.

Re: In The Works – Amazon Aurora Serverless

#18

Post by superasn » Wed, Nov 29, 2017, 6:07 PM UTC

Last week I created a small framework called lambdaphp[1].

My aim was to host a Wordpress or Laravel site on aws lambda without paying any monthly hosting charges. I got everything running (sessions, fs, request, etc) except of course I still had to use RDS and I think this takes care of it too. So now I can expect to run a full site which is only billed by the amount of resources consumed.

Of course my project was just for my own amusement but I think this is the way how it's going to be done soon or where Aws is heading. Seems pretty nifty!

[1] https://github.com/san-kumar/lambdaphp

Re: In The Works – Amazon Aurora Serverless

#19

Post by k__ » Wed, Nov 29, 2017, 6:29 PM UTC

mjb wrote: post #17

k__ wrote: post #15

Earlier quoted context omitted.

Can't you open the connection outside of the function? So as long as the function is hot, it won't reconnect.

That's right. Make connections to databases (and most other things) the first time your Lambda handler runs, and stash them in a static/global variable for re-use on future runs. That allows you to amortize the cost of forming the connection over many executions of your function, which improves latency, reduces cost, and reduces load on the backend.

Well, amortize sounds a bit funny when the first user basically has to pay the whole cold run, hehe

Re: In The Works – Amazon Aurora Serverless

#20

Post by meritt » Wed, Nov 29, 2017, 6:29 PM UTC

superasn wrote: post #18

Last week I created a small framework called lambdaphp[1]. My aim was to host a Wordpress or Laravel site on aws lambda without paying any monthly hosting charges. I got everything running (sessions, fs, request, etc) except of course I still had to use RDS and I think this takes care of it too. So now I can expect to run a full site which is only billed by the amount of resources consumed. Of course my project was j…

AWS will likely add PHP support, yes but they absolutely will not do what this project does: Running a NodeJS http server that launches a PHP binary and runs local scripts.