milliVolt infrastructure

We create lightweight infrastructure solutions for the web.

[milliVolt infrastructure @milliHQ]

@HuntEth16664821 Think the cold start in fargate is much higher than when using the regular Lambda service.
For Node.js the avg cold start time is between 0.2 and 0.4s which is hard to beat.
DDOS should not be a problem, since every request goes through CloudFront which is protected by AWS shield

[milliVolt infrastructure @milliHQ]

See what's next with our Next.js Terraform module:

- Atomic Deployments
- Integrated workflow for IT departments and developers

Learn more: https://t.co/EP7JHTXw2v

[milliVolt infrastructure @milliHQ]

@HuntEth16664821 Technically yes, in fact this is already possible with our image optimization module today.
It has the option to disable CloudFront, so that only the Lambda & API Gateway endpoint would be created, that can be used as origin from every CDN service:
https://t.co/kuVu5KTXVI

[milliVolt infrastructure @milliHQ]

We are now listed in the official Next.js documentation as #serverless hosting solution 🥰
Thanks to @leeerob and the whole @nextjs team for the recognition!

See it live: https://t.co/Wi9UXXa5kE

[milliVolt infrastructure @milliHQ]

@HuntEth16664821 But I am interested in hearing more about your use case, what do you think could fargate offer, that the module is currently missing? /4

[milliVolt infrastructure @milliHQ]

@HuntEth16664821 different cloud vendors and that's why we have chosen Terraform in the first place.
I would consider using fargate as a step backwards for this module since our solution provides a cloud native solution for Next.js without any middleware (containers) required. /3

[milliVolt infrastructure @milliHQ]

Wanna try out the new atomic deployments feature, but you're unsure where to start? 🤷‍♂️
We made a video that gives you an overview over the recent innovations and how to setup and deploy your first #Nextjs app to #AWS 💪
https://t.co/lg76ym6eIn

[Felix Haus @ofhouse]

Dropping a new video on the atomic deployments feature that is coming to #Nextjs for AWS 🎉
Full tutorial included, so if you have some time left over the weekend, feel free to try it out!
https://t.co/HsY8SQIfcn

[milliVolt infrastructure @milliHQ]

@0xPooka However this is not fully working right now as only the Lambdas are destroyed but not the static files on S3 for now.
Also the invalidation of the CloudFront cache is not fully working yet.
This is something that should be fixed in the coming weeks.

[milliVolt infrastructure @milliHQ]

@0xPooka Hey, thanks for the feedback ✌️
Yes, using this for branches or pull requests is exactly what this feature is built for.

Documentation is a bit behind, destroy is possible with `tf-next deployment rm`.
Same is for aliases with `tf-next alias rm`.

[milliVolt infrastructure @milliHQ]

How many Lambdas could fit into a single AWS account? 🤔

Find out soon with our unlimited deployments feature, which enables multiple serverless Next.js installations powered by a single CloudFront instance.

[milliVolt infrastructure @milliHQ]

Would be great if that could be set to something more reasonable (e.g. 100 or 250) for new accounts so that the reserved concurrency could be used without contacting the AWS support.
3/3

[milliVolt infrastructure @milliHQ]

@AWSSupport Hey, we've noticed that on new AWS accounts the concurrent executions quota (L-B99A9384) has been drastically reduced (Below the default quota).
1/3

[milliVolt infrastructure @milliHQ]

Since 50 is the minimum account value, you can't create a single Lambda with reserved concurrency without requesting an increase through support, which affects some of our users: https://t.co/WZpXGK4hM3
2/3

[milliVolt infrastructure @milliHQ]

(2/2) We plan to offer packages for express, koa and Fastify and also a dedicated docker image.

This way you can build & scale the image optimization in your stack independent from your Next.js app.
Learn more: https://t.co/HNpxZpN0Zk

[milliVolt infrastructure @milliHQ]

✨ Next.js image optimization v12.0.0 ✨

• Support for AVIF
• Introduction of Pixel (See thread)
• ...

Full changelog: https://t.co/eXmOYcuATG

#Nextjs #AWS #Serverless

[milliVolt infrastructure @milliHQ]

(1/2) The layer that abstracts the image optimization from Next.js is now available as a standalone package called pixel.

With pixel, we aim for making image optimization work with more platforms other than AWS Lambda.

[milliVolt infrastructure @milliHQ]

New Terraform Next.js release (0.10.1) ✨

• Ensure correct invalidation for slug paths
• Adds new input variable tags_s3_bucket

See full changelog: https://t.co/S7bE1PhMQo

#Nextjs #Terraform #AWS

[milliVolt infrastructure @milliHQ]

New Terraform Next.js release ✨

• Host header in server-side rendered pages
• Removes random ids from resource names
• ...

See full changelog: https://t.co/IhRgIdIxrZ