You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🎯 Goal: - Allowing the user the choice between various technologies is at the heart of Practica. Fastify is a super-popular and great framework (a candidate to serve as our recommended web layer). We should add it as an alternative web layer to express, it will be located in a sibling folder and the code generator while stitching the solution will copy OR express OR Fastify as the web layer. This is agnostic to the domain and data-access layer which will always be the same
🤔 Things to consider:
Fastify serves as our web layer, hence it's responsible for JWT validation, and other web-related tasks. With that in mind, our existing libraries might need to change to support Fastify or maybe we should add dedicated new libraries?
Some existing functionality is built inside Fastify and in that case we should use Fastify without abusing it. For example, Fastify has a logger built-in and a validation framework
The text was updated successfully, but these errors were encountered:
@goldbergyoni yes. @DavidBK if you can create a PR from your fork to here, it would be great, then we can continue working on it and finish it together
🎯 Goal: - Allowing the user the choice between various technologies is at the heart of Practica. Fastify is a super-popular and great framework (a candidate to serve as our recommended web layer). We should add it as an alternative web layer to express, it will be located in a sibling folder and the code generator while stitching the solution will copy OR express OR Fastify as the web layer. This is agnostic to the domain and data-access layer which will always be the same
🤔 Things to consider:
The text was updated successfully, but these errors were encountered: