Is it so very wrong to think of "shortcut-circuiting" the architecture by not having to use an api server to access the database, and just use an existing http server to statically server the blazor wasm app? So, the security concerns are negligible in this case, also the data handled is not mission critical. This app must serve a small number of users (10 at max) and it's purpose would be to upload data from user input (either through forms or file upload) into an already populated database (postgres in this case). I have been given the task of developing a small app that feeds user data into an sql server accessible only on the local network. Now I work for a company that only runs only on-premise hardware and is running a small private server infrastructure. I acknowledge the fact that Blazor is a front-end framework and it should make use of proper implemented back-end api's to consume and deliver data. I know the question above must have been asked before, but searching for 20 minutes, and I can't find a good explanation (at least for a simple use case I have to deal with).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |