Somewhat OT: I want to create an auth system (username, password, login, logout) using a serverless architecture with Cosmos DB as data storage. Each user will have it's own document and logging in will set a flag in that user document, or maybe in a session document. Login with Facebook would also be nice. Anybody know of such a pattern or best practices?
There is a great authentication boilerplate that is set up for AWS. It might not be so hard to extend it for other platforms. Here is a blog post I did showing how to use the boiler plate with FaunaDB for authentication and authorization.
Doesn't sound particularly challenging from a serverless point of view, if you have some sort of central Cosmos DB instance. Wrap it all in a Lambda function.
Where would the event gateway be deployed? It looks like it could be any provider and anywhere right? Essentially, giving me the ability to take my entirely serverless architecture and giving me servers to manage. Alternatively, it may be a Kubernetes type deployment. OR, what my guess is, the first step towards getting people to use the serverless platform, which will handle hosting this for us.
Im wondering what are the use cases here. Why someone would keep different functions in different providers while she requires the communication between them.
The example given at the emit conference was: You have a lot of code running in AWS, but all of a sudden, you would like to start using some nice features around google ML, and for this you need integration with google cloud.
Over a longer period, the idea is that there is an oligopoly of PaaS providers and if their features don't match 1:1 perfectly, your business may need a hybrid approach.
* Cost based configurations
* Putting high compute in one cloud and storage in another?
* Perhaps to handle entire cloud outages?
* There may be features that don't exist across all the providers that people may want to take a dip into.
* Integration w/ existing frameworks, AKA code deployed to multiple clouds that need to be supported.
[+] [-] 21|8 years ago|reply
[+] [-] jchanimal|8 years ago|reply
https://serverless.com/blog/faunadb-serverless-authenticatio...
[+] [-] mayank|8 years ago|reply
[+] [-] pesfandiar|8 years ago|reply
[+] [-] heffay|8 years ago|reply
[+] [-] brianwawok|8 years ago|reply
[+] [-] Myztiq|8 years ago|reply
[+] [-] mayank|8 years ago|reply
[+] [-] sscarduzio|8 years ago|reply
Not a mention of this in the article..
[+] [-] kostarelo|8 years ago|reply
[+] [-] nichochar|8 years ago|reply
Over a longer period, the idea is that there is an oligopoly of PaaS providers and if their features don't match 1:1 perfectly, your business may need a hybrid approach.
[+] [-] Myztiq|8 years ago|reply