Difference between User and Account object in social network design?

Question

I am creating a data model for a social networking site and have lost the way of modeling users and accounts.

1) The user signs and creates an account. Thus, we assign the user the user ID, as on most social sites that we see, which are the same profile identifiers. Now is this an account id? OR is there a hidden account identifier? If a user can have multiple profiles, then the user ID is separate from the account ID, which is separate from each profile ID?

2) Assume that 1 user has only 1 account. But when the user edits his account or allows the administrator to edit the user account, does the user edit the account, so does it require two separate identifiers to simulate it?

3) What is the life of the user and the account object? If a user closes his account, does this mean that both the user and the account object will be killed?

4) And who contains the user profile data, user settings, privacy, friends, etc.? User object or Account object and which object is superior?

5) Are there system objects, such as photos, videos, etc., that the user can create / admin, as well as those that belong to the user or the account object?

6) What exactly does the object do? Say we have status updates, comments, profile data. Are these 3 objects? Or all considered 1 type of object and only 3 categories?

Answer 1

I understand your point of view about the user and profile, but user and account?

For most of my projects, this is the same. Most of your questions seem to stem from this confusion. Why do you need separate identifiers? Why would you separate them. If you have a need, then perhaps so. For example, you might have a user account that spans multiple services. This user has separate account information in different services, but the same login. In this case, you need to have two separate objects: login (in the authentication system) and account (in a real application). But I do not think that you are creating such a large system. No?

6) If all of them cannot be represented in one code, they should be separate objects or received from a similar object. For example, on some portals, I see that the PM (private message) system looks like a private forum between two or more people. Without looking at the source, I would suggest that the topics or topics of the forums are the same or similar, possibly from the same object.