Thank you, as always your content is very interesting, I'm studying architecture and improve my NextJs projects, so I'm grateful for your channel, I subscribe!
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?
Thank you! I'm not an expert on this, but as far as I understood argon2 is faster and more advanced, while bcrypt is a bit slower but more widely adopted. bcrypt apparently can suffer from GPU-based attacks (no clue what those are 😅) whereas argon2 is immune to those. Maybe there's a better argon2 alternative out there that's runtime-agnostic like bcrypt, but for now bcrypt will have to do.
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.
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.
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? 🤔
Thanks! The controllers are def important because usually they orchestrate multiple use cases. That's considered logic as well, so if the web, api and cli implement the order of the use cases by themselves you're creating opportunities for bugs. The order of execution is always the same for a specific operation, so you should implement it in a shared place - the controller. In regards to having multiple projects, you don't need to implement 3 controllers, unless the difference between how those projects render the information is too big.
@ thanks for reply! Not sure about the bugs if let’s say all use cases have been unit tested, for the actual app we can simply mock them. Usually controllers share the same logic but different view/presentation. Anyway, keep it up with the videos please - that’s golden! 👍
Thank you, as always your content is very interesting, I'm studying architecture and improve my NextJs projects, so I'm grateful for your channel, I subscribe!
very niche topic but that’s what i was looking for. thanks for the video
great thanks for explaining the change.
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?
Thank you! I'm not an expert on this, but as far as I understood argon2 is faster and more advanced, while bcrypt is a bit slower but more widely adopted. bcrypt apparently can suffer from GPU-based attacks (no clue what those are 😅) whereas argon2 is immune to those. Maybe there's a better argon2 alternative out there that's runtime-agnostic like bcrypt, but for now bcrypt will have to do.
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.
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.
Thanks Evyweb!
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? 🤔
Thanks! The controllers are def important because usually they orchestrate multiple use cases. That's considered logic as well, so if the web, api and cli implement the order of the use cases by themselves you're creating opportunities for bugs. The order of execution is always the same for a specific operation, so you should implement it in a shared place - the controller. In regards to having multiple projects, you don't need to implement 3 controllers, unless the difference between how those projects render the information is too big.
@ thanks for reply! Not sure about the bugs if let’s say all use cases have been unit tested, for the actual app we can simply mock them. Usually controllers share the same logic but different view/presentation.
Anyway, keep it up with the videos please - that’s golden! 👍
does the edge runtime it’s going to make the bill expensive?
It's billed differently, so it all depends on how much traffic your site gets. Definitely not a must-have, but it's just another option out there 😁
Thanks for the video but all of this looks more like over engineering than clean architecture.