| Tweetovi |
|
Guillermo Rauch
@rauchg
|
38 min |
|
I'm a huge fan
|
||
|
||
|
|
Guillermo Rauch
@rauchg
|
1 h |
|
🔥
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
2 h |
|
Yosemite. Basically the best place on earth.
|
||
|
|
||
| Guillermo Rauch proslijedio/la je tweet | ||
|
Sriram Krishnan
@sriramk
|
15 h |
|
|
||
|
|
Guillermo Rauch
@rauchg
|
17 h |
|
Enterprises are happily using the platform because not managing purges and infrastructure gives them better performance and availability.
Adding network hops and coordination results in headaches. I touched on this here:
rauchg.com/2020/2019-in-r…
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
17 h |
|
We do this routinely with no issues. The missing cache goes to our highly-available storage system for the generated pages (if you are using SSG)
If you are not using SSG, yes, we purge and then your functions will be invoked, but it's trivial to cache inside functions too!
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
17 h |
|
In traditional CDNs, you are usually forced to set a `max-age` that impacts both the CDN layer *and* the customer. You tend to lose control.
If you use the specialized `s-maxage` flag, then you are forced to purge yourself.
That's the concern we automate and remove stress from.
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
17 h |
|
I think it's key to add nuance to "caching"
By default, all your assets are cached at the edge. They get purged when you re-deploy
We don't set any defaults with regard to caching on your client devices. In fact, we believe clients should always get the *freshest*!
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
17 h |
|
You can definitely do so, but you don't need to. That's why the CDN is integrated.
The page I linked details in-depth how to customize.
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
18 h |
|
Caching is automatic. There's absolutely no need to customize headers, that's one of the most interesting features of the platform… All static assets go to the edge, and purging is automatic/realtime.
For functions, just return `cache-control`:
zeit.co/docs/v2/networ…
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
18 h |
|
Yep! Basically producing those is what the JS bundler is already good at for the client side ("common chunks"), so we can extend it for functions 🔜
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
18 h |
|
You could even generate function *layers* of common deps for even faster boot times and deploys 😲🤯
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
18 h |
|
Obrigado
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
21 h |
|
Something that might be helpful is recording all outgoing HTTP requests by using web inspector while navigating all pages.
Then re-play all those requests later in bulk.
|
||
|
|
||
| Guillermo Rauch proslijedio/la je tweet | ||
|
derrick reimer
@derrickreimer
|
22 h |
|
Payments are officially in early access!
statickit.com/payments twitter.com/rauchg/status/…
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
22 h |
|
Wow! @StaticKit is gaining the ability to accept payments 🔥
📵 Nocode implementation
😌 Users don't leave your site
💳 Powered by Stripe
🎨 Only frontend skills required
🔌 Integrates easily with @zeithq
stripe-react.statickit.now.sh
Nice job @derrickreimer pic.twitter.com/mI9qsy2hh5
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
23 h |
|
the feeling of a monolith*
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
23 h |
|
Correct. Combining static assets and functions in one repo gives you the feeling of a monorepo w/o any of the downsides.
Faster rolls, pushing static parts directly to the edge, individual functions for each API endpoint, etc.
|
||
|
|
||
|
|
Guillermo Rauch
@rauchg
|
5. velj |
|
Wrap your exported page’s component in it? Not sure I understand fully. cc @_ijjk
|
||
|
|
||
| Guillermo Rauch proslijedio/la je tweet | ||
|
Eric Eriksson
@ericeriksson
|
5. velj |
|
god damn @zeithq I can't recommend you strongly enough. Zeit Now is down-right magical and Next.js just makes so. much. sense. Thank you for removing so much of the mind-numbing struggle that comes with React.
|
||
|
|
||