Up - Deploy serverless apps and APIs in seconds to AWS Lambda

@engmsaleh good question! The primary difference is that Up is designed specifically for existing paradigms, you write your app/API as you always would locally with any HTTP framework you like, and then `up` to deploy it. You could think of it as a serverless Heroku, letting you test apps locally very easily and use existing knowledge. Serverless (and others) by contrast require specific knowledge of the serverless ecosystems, where you're managing individual Lambda functions per-route, and writing your application to fit that model. I don't have remote debugging functionality right now, I'd have to look into that.

@tjholowaychuk I'm personally using serverless framework and I agree with you as a start it is a bit of challenge I will give Up a shot In my opinion one of the most struggles that I have found when developing serverless in general is debugging if you make Up work for that I think it will be a huge addon 😄

@engmsaleh @tjholowaychuk : Thanks for this Q&A. I always had this doubt myself about Up. So if I've understood it right - Up takes any http based app and makes-or-deploys a lambda (aws serverless) version of it ?

@engmsaleh @o1lab yep that's correct. Technically what it actually does is run your application inside of Lambda, via `node server.js`, or `./main` for binaries etc, and Up has an internal proxy which takes the Lambda API Gateway event, and translates it back into HTTP, forwarding it to your server. This is what lets Up provide middleware features such as CORS, logging, redirects, error pages and gzip compression as well. It sounds like it would introduce latency, but in practice it's very low, typically less than 1ms.

@tjholowaychuk WOW ! That is really seamless !! The title in Up github is selling it short for me 😀 ! >>> Deploy ANY apps, apis, and sites within seconds as serverless in AWS (would be great) I've played with GCP cloud functions and had come across serverless.com framework. The whole concept of writing yaml in serverless.com is really not it. PS: Im a big fan of your work 😍😍 - Great moment for me to have interacted with you😀

@tjholowaychuk We've been using up for over 2 years for multiple projects. It just works amazingly well! Well done

@tjholowaychuk Oh... and I've written about the experience here https://hackernoon.com/lessons-l...

@vandanic yeah the logo part was unfortunate, mine is supposed to be an "A" but kind of looks like a triangle. As for the aesthetic in general, I've always had a minimalistic monochrome style, long before Zeit existed. Hell their v2 stuff looks a lot like Up, it's basically a router in front of Lambda.

@vandanic @tjholowaychuk You gotta go w/ bigger fonts for us old timers. The tiny sliver fonts are really really hard to read for those of us who haven't yet made the journey to reading glasses.

@petebray ahah noted, thanks!

@vandanic @technodevochka I remember using up for quire a while before zeit was around. His design style has been consistent for many years, I agree that @tjholowaychuk was first.

@vandanic @technodevochka yes tj was first, and got something that works perfectly. I ended up on Up after huge frustration trying to run things on zeit v2. Their v2, not only being an horrible breaking change, does not work as (loudly) advertised. And not only being first, i'd say, reliable

@ninalimpi thank you 😸

@adrian_mejia I haven't used Now v2, but from the looks of it some major things would be: - Up runs in your own AWS account, so you get complete isolation, security and don't have to worry about third-party infrastructure going down - Up lets you deploy regular HTTP applications, you can generally take an existing Express.js app for example and just run `$ up` - Much cheaper logging, Now's logs are very expensive in comparison, Up's are just AWS' $0.50/gb—charging per line is a bit extreme, they add up very fast in real apps - Up follows industry best practices of infrastructure-as-code, up.json contains dns records etc, instead of defining them via CRUD commands - Up is one flat fee, and can be used for any number of applications, no per-seat pricing - Up's support is included in Pro, Now's is very expensive - Up has alerting for errors and so on, I don't think Now has metrics in general, nor alerting - Up has stages (production, staging, etc) and instant rollbacks, Now uses a more convoluted deployment scheme - Up has pretty comprehensive structured log querying capabilities, I'm not sure what Now has on that front, looks like only substring matches for queries - You can take advantage of the 1,000,000 free requests/mo on AWS - Now may have slightly nicer UX in some scenarios due to AWS limitations, for example AWS makes you verify ownership of a domain name via email for the free HTTPS cert - Now has a higher upper limit on the duration of a request — 5 minutes, vs Up's 30s, which is an API Gateway limitation - Now has nicer static site support, though Netlify.com is more feature-rich than Now and free I think that covers the bulk of it, happy to answer any questions!

@ji didn't realize you were using Up! haha thanks for the comment :D

@simon_mansfield thanks Simon!

@kieran thanks a lot! Glad it's working out 😄

@tanakasamuel thanks :D glad you're liking it!