Remember last week when I mentioned moving the whole server logic from AWS into my Nuxt app? I hoped that it will not cause any issues. Well, it did. 🤦🏻♂️
The current server is configured with 512MB of RAM, but sending the weekly newsletter took more than 1GB of RAM, and my server crashed. I triggered the API endpoint on my local machine to send the newsletter, and it worked fine.
After careful consideration, I decided to move only the email sending process to an AWS Lambda function. This function is triggered by the Nuxt app, ensuring that the app is not hindered by the email sending process. This solution not only provides the server with sufficient resources to handle other requests but also proves to be a cost-effective alternative to upgrading the server. 🚀
👉🏻 In this talk, you get introduced to FormKit — a form-building framework — and how it can empower Vue developers to write consistent, accessible, even delightful forms.
👉🏻 Learn how to create functions that adapt to await usage, enhancing your understanding of Nuxt and empowering you to apply these patterns in your own projects.
Nuxt provides the setResponseStatus composable to set the status code (and optionally the status message) of the response.
This composable only works on the server and will have no effect on the client. Additionally, it can only be used in the Nuxt Context. The Nuxt context is only accessible in plugins, Nuxt hooks, Nuxt middleware, and setup functions (in pages and components).
eventevent will be undefinedundefined in the browser, so you can safely use this composable in your Nuxt context.
In my client's project, I used this composable to set the status code of the response to 410 when a product has expired. This way, the search engines will know that the product is no longer available and will remove it from the search results:
👉🏻 This post dives into the mechanics of Promises, their states (pending, fulfilled, rejected), and how to work with them using the .then() and .catch() methods.
评论
发表评论