I nave a Nuxt app generating a website for events. In the newarby future the website will host a 50.000 audience within 4 days. Most of the data is populated during nuxtInit, therefore serving a static website with Netlify, fully generated before does not seem to be a problem. However this particular event also needs some special pages with custom design. In order to limit de work needed to accommodate this design and content challenges we decided to extend the the content about our item with Storyblock, meaning each page will have an associated ID from our source.
The content provided by Storyblock should be delived in a manner or real-time or as best as possible. As far as I can read, Storyblock has a limit of 6 requests / second, which obviously will not make it possible for each user to request the content in the client side, therefore some questions appear:
- is it better to make the requests through AWS API gateway and put a caching layer in from?
- how does the Storyblock memory work for nuxt on a client side enviroment? is there any caching?
- should I just put an AWS cron job that delivers the message via graphql subscriptions?
- should I create a cron job that exports to S3 and have a caching layer on that?
What would be the recommended solution to takle this? even if it’s not listed above?