It looks like up for running something like express/koa/etc while fx is for functions (like AWS Lambda). They are both "serverless" but that's about all they share in common AFAICT. Thanks for mentioning "up" though, I'd never heard of it before, very cool.
Yep it uses AWS Lambda currently, you'll usually end up paying < $1 for small side projects such as https://gh-polls.com/ etc, but it definitely depends on your traffic.
This project looks like it's more FaaS style (sans the self-healing / autoscaling etc). Up is more application oriented, it just happens to use Lambda.
Sorry if I mistunderstand. The readme is very limited. But this need a (vps or something) server that I own / manage ? It does not seem to upload the functions(s) to some cloud ?
In general I think 'serverless' means deploying code without managing some kind of server yourself.
I think serverless refers to the use of 'lamdas' as the unit of deployment, as oppose to containers or VM's, but someone else may want to add/edit that.
README is not quiet clear, but for my understanding, lambda is kinda thing that helps you to do serverless, but lambda is also running on some kind of server maintained by AWS, right? fx is kind of lambda, but owned by yourself.
Well, yes, you can run your own server to provide yourself a serverless platform, but it kind of defeats the purpose... Since then you end up having to maintain your server anyway.
I suppose there may be a point to it if the serverless platform is extremely stable and never has any security issues or other things to update.
Your guys are so right about fx’s ‘Poor man’s README, I will update it soon. Long story short, you can deploy fx on a host (cloud or localhost), then you can deploy a function to be a service in few seconds, just like AWS lambda ( but Poor man’s lambda).
19 comments
[ 6.8 ms ] story [ 68.1 ms ] threadhttps://github.com/apex/up
This project looks like it's more FaaS style (sans the self-healing / autoscaling etc). Up is more application oriented, it just happens to use Lambda.
In general I think 'serverless' means deploying code without managing some kind of server yourself.
(“Serverless”, at least to me, means a platform where I don’t have to worry about running servers.)
I suppose there may be a point to it if the serverless platform is extremely stable and never has any security issues or other things to update.