FAQ about up HOT 13 CLOSED

Hahaha good to hear, should be a fun little project to hack on! I'll try and get the first release out in a week or two :D

from up.

@muhajirframe correct, it'll be similar to Heroku / Now / Google App Engine etc in scope and user experience, but hosted in your own AWS account. I haven't pushed the code yet since I have a few things to implement first and QA everything so people don't just run into issues right away, better no code than half-implemented code :D.

It's also being built to abstract the provider entirely, so in the future you could up to Digital Ocean, Hyper.sh, Google, Azure, etc. There will be some things those platforms don't provide such as built-in middleware for logging, CORS, compression (gzip, brotli), various static site middleware (headers, rewrites, asset minification, fingerprinting), global deployments (to 1-13 regions), logging / metric providers (papertrail, loggly, datadog), among other things.

After pushing the code I'll build a comparison table so people can see what the limits are, its strengths / weaknesses, some timing information for how long deploys take etc.

from up.

@stevelacy primarily the "serverless" aspect. Convox is sweet but ECS ends up being too expensive for people like myself, and generally the ease of managing / scaling Lambda is super trivial. Some of the middleware / frontend features will be reasonably unique to Up as well, I haven't seen any that behave like a reverse proxy (caching, CORs, redirects, rewrites, asset compression, fingerprinting, etc).

from up.

I'll be adding more info such as latency, cold start timing, etc but https://github.com/apex/up#pricing has a bit of a comparison for now, might add Firebase too, any others?

from up.

ah! yes totally forgot about Surge

from up.

Would love a "How To: Global Distribution" as part of this. In my book, one of the most appealing features, and I'm sure others (like myself) aren't going to know how to get the most of Lambda.

from up.

Just wondering, how different would Up be from convox and their rack? (We currently use convox, and are eagerly wanting a better replacement).

from up.

How will Pro's "In-Memory Caching" work? Is that a global & configurable cache or is it a one-size-fits-all approach for all routes? Also, I'm curious about where the caching will take place & if responses served from cache will count towards my Lambda usage metrics.

Thanks! And sorry, hard to contain excitement~

from up.

Might swap that one out, since API Gateway has a cache feature it should be a simple configuration, but caching in the lambda itself would be cost effective that's for sure, I believe it respects HTTP caching though so it should be "global", I'll double check! Hope so at least haha

from up.

Hi @tj , i am pretty confused with this project. Does it works like zeit's now? You just type up and everything is up? And also i found there is no code on this repo, is is intended? And how can I install up?

from up.

Oh my god! , I have been waiting for this 😂😹 . +999 for this project.

Okay, when will this be released? I mean time estimation maybe?

from up.

I have two other suggestions:

1. Explain the differences between Up & Apex, and when it's more appropriate to use one vs the other. While this may be obvious for some, it won't be for the majority -- esp those without AWS backgrounds.

2. Add a(ny) DB integration example. Could be a dead simple API endpoint that serves from a DB query. Most likely pairs best with the "How To: Global Distribution" from above.

   Global API responses + global DB replication = game changer.

from up.

Surge is also popular.

from up.