@keremeki13
Nothing here yet.
Nothing here yet.
No blogs yet.
Thank you for answering me. You are right also in that way we avoid create duplicate data. I like this feature of json Field but I don't know if Spring JEE ORM support that or not I might switch database because of that. but what about saving this data in json file in backend is that bad?
thank you so much forr the answer. Yes it is consumed only by my Front-End Web app so going with local storage is secure enough? (I want to store there refresh token so when access token not working I'm going to refresh it.)
Thank you so much for the reply. I finally understand completely what did you say. First when I thought of this architecture I knew something wasn't correct that's why I asked here. So like you said mobile application sends the data to server then the server if he gets any request then he check which FP reader send it then check FP and return the result. Easy and can be done by RESTful only. About the architecture I will read about it in details. Thank you again.