Introducing Cloud Functions for Firebase

Re:Introducing Cloud Functions for Firebase by lotyrin on Thursday March 09, 2017 @02:44PM (#13832661)

Any service with more than 400 users that want to run a batch process for each user in constant time with respect to number of users.

[ Parent | on HN ]

Re:Introducing Cloud Functions for Firebase by inlined on Friday March 10, 2017 @02:51PM (#13841514)

Wouldn't this still require linear time to scan a database and map users to work?

[ Parent | on HN ]

Re:Introducing Cloud Functions for Firebase by fiatjaf on Thursday March 09, 2017 @02:52PM (#13832783)

Right, how many of those do exist with an internal architecture that will fit the Lambda model?

[ Parent | on HN ]

Re:Introducing Cloud Functions for Firebase by ruleabidinguser on Thursday March 09, 2017 @03:21PM (#13833124)

I'm curious more generally why would somebody use Lambda at all? Surely its far more expensive than running on your own servers (or instances), no?

[ Parent | on HN ]

Re:Introducing Cloud Functions for Firebase by ceejayoz on Thursday March 09, 2017 @03:36PM (#13833301)

Lambda's billed in 100 millisecond increments. EC2 servers are billed in one hour increments. If you need short tasks that run in bursty workloads, Lambda's (potentially) a no-brainer.

[ Parent | on HN ]

Re:Introducing Cloud Functions for Firebase by imtringued on Friday March 10, 2017 @07:55AM (#13838214)

Firebase users don't want to run their own servers.

[ Parent | on HN ]