High Level Architecture #2
Replies: 5 comments 4 replies
-
Beta Was this translation helpful? Give feedback.
-
Looking at the above diagram, we need to discuss the following points
If you have any other points feel free to discuss them as they come in your mind. |
Beta Was this translation helpful? Give feedback.
-
Where we placed master key though which we manage password app? I suggest it will be placed in config files just like I did for for alumni db password in web.config file. |
Beta Was this translation helpful? Give feedback.
-
I feel like we should not use any server client architecture for our app. Let me explain it to you, if we kept the data on a server still its someone's data living on someone else's machine. So what I propose is that we don't use client server architecture for our App. Now the question arises if we don't use the client server architecture then what do we use? The answer to this question is that we go server less which means that we write the user passwords and data on a text file and then encrypt the file and keep it on user's device. And when we need to read the passwords we decrypt the file and we read the data. In this way the data will be secured and it will live on user's own device. We should also give user the option to upload his encrypted password file to a cloud storage service e.g. dropbox, google drive etc. Feel free to ask if you have any questions or something better to share. |
Beta Was this translation helpful? Give feedback.
-
I think that the mentioned architecture #2 (comment) seems ok and we should go for it |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What should be the high level architecture of the system?
Beta Was this translation helpful? Give feedback.
All reactions