How I Deployed a Clean Architecture Next.js App to Vercel Edge Runtime

--

--
00:00 - Intro
00:40 - Why we couldn't deploy on Edge
01:06 - Replacing argon2 with bcrypt-ts
02:33 - Why I didn't pick typed-inject
05:29 - Implementing ioctopus
09:23 - Registering controllers and use cases in DI
14:21 - A brief mention of eslint-plugin-boundaries
16:13 - Making it official

[devyb-cc]

as always nice insights, there are not many persons in webdev who do proper clean architecture setup for video demos.
i hope you are also covering other meta frameworks with clean architecture.

[zhxnrs]

very niche topic but that’s what i was looking for. thanks for the video

[prashlovessamosa]

great thanks for explaining the change.

[KeyserTheRedBeard]

Impressive content, Lazar Nikolov. Looking forward to your next upload! I hit the thumbs up icon on your video. Keep up the fantastic work. The transition from Argon2 to bcrypt TS for edge runtime compatibility is fascinating. How do you anticipate this change will affect the overall security model of applications using clean architecture?

[Evyweb]

Thanks for the video ❤ you can pronounce it like in "heavy web". For bcrypt, you can also use it directly inside authentication service so the use case doesn't depend on bcrypt (infra) but on the authentication service port. And if you need to change it by another lib, you have only one place to change. Great job and explanations thanks.

[bazikmail]

That’s cool, thanks for the video! But I would argue that controllers are a bit too much, you simply pull the use cases inside of your actions and that’s that. So your domains/modules should only contain the business logic/units. Imagine you have 3 apps: web, api, cli - would you write 3 controllers? 🤔

[dorutu]

does the edge runtime it’s going to make the bill expensive?

[curiousprogrammer]

Thanks for the video but all of this looks more like over engineering than clean architecture.