How to design a database design class (LIVE Class)
![](https://i0.wp.com/allprowebdesigns.com/wp-content/uploads/2023/11/1699257755_maxresdefault.jpg?resize=840%2C430&ssl=1)
Video Title: How to design a database design class (LIVE Class)
All right uh so like I mentioned the whole essence of database design comes from understanding very deeply the project at hand what are we doing the project at hand so you have to understand that very you know um deeply concisely and of course comprehensively um now your
Job um plus maybe the DBA job will then be to create a data structure or the architecture dat architecture that data flow that can that is able to achieve that goal all right and doing so you have to one thing you have to put in mind when you’re doing so is to avoid
Redundancy redundancy in the sense that you don’t repeat data that you’re keeping somewhere you don’t have to keep it multiple times in the same database um you want to keep it once and make use of it reference it where where it’s that data is needed you don’t want to keep
People’s um people’s information um certain information multiple times in different compartment so you want to keep it in one compartment if it is needed in another compartment then you share it with that compartment that needs it all right um so this is what you have to keep in mind when you are
Doing the design and then each compartment will have a name and then you’ll give them comprehensive details all right so um the best way the approach for us to understand all these roles user type one to many many to many um signing up with some data and then I
Will reconcile the data these are the questions that you guys ask will be for me to use one of your projects as illustration so feel free to give me anyone any of your projects um who talking let’s use I said I said you pray everybody is praying up their own
Uh you said what iss okay sir um I said try you said what AA you said Drive first I said for uh okay so let’s just go with one it doesn’t matter we are not going to finish the whole design uh but the most important thing is for you to understand
The concept is it py pay we are going to for let’s look at py uh yes sir if you look at pip so explain to us what py means Aisha don’t worry don’t worry just let’s just Let’s do let’s I I think your Tri trive is what mental health support mental health support
Yes uh um how many of you guys are here two I am how many of you guys are here huh we yeah are three okay let’s do let’s let’s do TR so explain I shall explain what what what what are the what’s just summary in essence what’s your your project is about okay
It’s like this yes yes okay so it is a mental health basic our main features are therapy connecting um Specialists with people that have medical and mental health concerns to um therapist on their own schedule right they they will meet them virtually we have options of them
Either doing audio call video call or chatting with them then our second main feature is relaxation which basically the same grou raat yes sir oh okay okay okay so basically basically you you connect people that need um medical checkup like but basically you your your your or you specialize in mental related checkups
Right yes sir yeah you you’re not doing any other thing exra just mental health related checkup right and then you are sorry someone is okay okay Sobe I should to him toide the yeah yeah I think I I will check with him also all right fine okay um
So um sorry the tribe is we are connecting patients with doctors uh that need medical patients that need medical mental health checkup with doctors right and then based on their schedule and then they will pay right AA yes sir just summarize it in just summarize say it in 2 minutes again
Please so that everybody understand understand your project but everybody else understand so they know the basis to which we are doing what we are doing yes so our app and basically helps with mental health issues with our main features such as therapy relaxation mood tracking and resources which contains articles videos
And audios those are our main features which is targeted that you know people facing mental health issues to help them achieve mental Wellness okay all right so thank you very much please is there someone who is not in AA group and does not understand Aisha’s Thrive project before we start because the it
Starts with the understanding like I mentioned of the project at hand so it doesn’t matter if it is your project it doesn’t matter because of course when you begin to write back ends different project will come so you need to be able to know how to attack and how to start
You know um any of this project so but like I said it has to start with understanding so is there anyone here who doesn’t understand the trive concept before we start breaking it down yes sir so you do you do not understand it yes sir okay so let me let
Me try to explain what um Aisha said so trbe is a platform that um connects people with mental health need with therapist they do so at therapist schedule they will go online and book an appointment with a therapist and then uh the ter and the appointment
Could be maybe they want to have an audio call with a therapist they don’t want to have a video call with a therapist or a chat consultation with a therapist before they able to do that they pay to have access to uh Consulting with the therapist um additionally they have a
Mood tracker you know where patients are able to document their mood uh on daily basis uh whether they’re happy they’re sad and whatever stressed and all of that uh is documented and therapists can uh follow up with their moods and they equally have access to articles
On the platforms that they can come and read um articles on the platform all right um Aisha is there anything I have not captured I think holistically captured it yeah Z so that’s that’s their project do you understand it now yes sir 100% oh okay is everybody else that doesn’t understand their
Project now so if we all understand their project the first thing is then to look at that project and start from the stakeholder what are the various stakeholders of that project uh and when I mean stakeholder I mean it as the various um users of that project of that application what are the
Various users of that application anybody Prosper Prosper you if you are talking can’t hear you yeah Mustafa go ahead let’s be fast so that this call can be short yes sir the mental um mental so Mentor patient is a user right good yes sir and who who
Else um the therapist the therapist is also a user great okay so that those are the two user types that we have yes sir I know the two user type that we have do we have any other type of user sir I was wondering if admin would
Also very much the owner of the platform the owner of the platform is also a type of user they are the one that will be creating um the various managing the platform basically um putting rates how much this person should be charging you know basically the owner of the the owner of
The the owner of the platform okay the owner of the platform are equally a user type uh user type so these are the various stakeholders the various users of the application the administrator of the platform which are the owner of the platform the patients who need medical
Um uh therapy and then the guys who do the therapy um that the therapist themselves so you you identify that now having identified that um you but you know that all of them are all users you’re not going to create one as uh um differently keep in mind you don’t want
To keep the same type of data multiple times um Aisha you you raise your hand yes and I wanted to bring it to your attention that in case maybe you open the documents we are not seeing it on your screen really um you are not seeing anything on my
Screen no no we are seeing your screen but I thought maybe you were writing the users down no no I’m not I’m just explaining can see your you can see all these Road all these Road yes we can see yes okay so I haven’t been writing anything
Yet okay so um so we understand that so let’s start from that angle so we have what we need we need users on the application that is pretty much like a modu uh based on what they have they they have consultations consultations these are various consultations whether audio video and
All of that they have what they call articles they have what they call mood tracking they have what they call let’s say mood in no particular order I just prefer to bring it here so let’s say we have mood uh depending on how you have it
Like that so let’s say we have mood we have articles as well so this these modules will be expanding as we grow along um talking about one uh so basically users of the applications who need their moves to be tracked and then there will be consultations and then
There will be articles now let’s let’s expans shate on user let’s take take user now so if you take user what are the various property of um a user what are the various property of a user that you want to keep now this might vary from one application to the
Other and you don’t want to keep stuff that you do not need for every property of that you are keeping about about an entity there must be a reason there are there you don’t want to say maybe we will need it later if you need later
What would you need it for you can you should be able to explain it even now you may not be using it now but you know why you you’re keeping it why it to be needed so you have to keep that in mind and of course since you’re using a
Method you can always hitrate and expand on your properties the properties of uh each of these entity each of these will be called an entity user is an entity mood is an entity consultation is an entity article is equally an entity I you are raising your
Hand okay that was a mistake I didn’t to drop yeah that was a mistake okay great so for each of these entity they would have what we call the ID which is a unique identifier of each of the record so that is number one on the list don’t negot
Nonnegotiable for each of these property you’re going to have it ID that recognizes or identifies each of these record uniquely so that’s the first thing you want to keep other is other is then based on the need of your application now remember that we are keeping all
User type have ini isue we are keeping them together all user all users in one um in one compartment depending on irrespective of the type of user that they are we don’t want to say doctors and we say first name last name email like that we say patient first name last
Name email when we are doing that we are repeating we have repeated uh couple of these property which could have been kept in one compartment you’ll see some designs and you see them like that you understand the application works but there’s a lot of rany a lot of rooms for error and
Then there’s no optimization so what I’m saying is that other person might want to be design might want to design this and say that um they have patient table they can say they have patient table they have doctor table and um maybe they have admin table now on the I’m explaining that’s not
What we are doing but I’m I’m I’m telling you why we are doing it our own like this so another person can come and say they have patient table patient table and then in the patients they will say they are have let me come down here
Let me not do it up there let me come down here in the patient table they can they will say they have they have maybe the ID of the patient they have first name of the patient or full name if they taking it full like that but it’s always
A good idea to have the name separated since it’s a medical um related so we have first name you want to know first name for the last name uh you may have something like that middle name middle name guys am I still connected I think I got
Disconnected let me see how much more we can record on okay now so I’m explaining um I was explaining the questions that Prosper asked about why we say that being a coach is a user type and um being a fellow is a user type that you’re trying to
Reconcile uh so how you you get to reconcile that is that there are certain things that as uh are are unique to some type of user you know there are certain things that are unique to some type of users what they are able to do uh irrespective
Of their role irrespective of their role what they are doing on the system just like when you go to university there’s no ambiguity whether you a student or a lecturer there’s no ambiguity so in it you is either you’re a lecturer or you’re a student you know the same thing here
Here when you when you when you go to the hospital with the person you meet is that the person works as an admin officer in the hospital the person works as a doctor or the person is a patient you know so this is this is this
Is it this is how you resolve that so there why you call down someone a doctor is because it has certain uniqueness in type of activity that he carries out on the system the same thing if you relate that to to thail for instance you have some users who have you know certain
Uniqueness in in terms of the activities that they perform in t lab activities for instance someone come to class um this type this type of users come and you know uh they teach and then beyond teaching for instance now I I maybe I equally assume a role
Of uh reviewing in the Council of Health other chamber you know all those stuff like that now similarly if you look at students and that’s are fellows that we call fellows um they have all fellows have the same type of activity that they perform additionally some fellows now
Have additional tax of carrying out some responsibility now if you set up the system you know you as a designer when you set up the system and what you call when you assign to me you assign role and you call that role um a coach it’s not wrong it’s not wrong
But you have you have an equalent tax to be able to then resolve other roles things that actually rul on the system with the type of user because you have used a type what you are supposed to use as as a type as a role and again
How this will be used is when people log in on the front end they will be showing them different type of interface when the patient logs in they will see patient dashboard they are not going to be seeing doctor’s dashboard how they would be able to easily resolve that is
Just checking the type of users that they are and then pushing them to respective dashboard when they are on on such dashboard they would then have roles for as an admin who goes to an admin dashboard does not have responsibility of doing everything because it’s just an admin user they
Will then do an additional check based on the roles and responsibil of that person to then know what the person can do and what he can’t and then display uh interface based on roles and responsibilities I don’t know if you get that yeah I understand it now yeah
Okay thank you sir you sound like a Prosper that I know before now from where don’t worry if if if it is a Prosper the Prosper would have we’ve done one application together before do you do development before Tyler yes you do flter no sir okay you’re not the prosper
Okay please any other question before we move on so that we build on what we have um in fact someone shared their ERD with me and they are almost on this on the right uh this thing IA shared what they they were able to do over the
Weekend with their dist um I’m sure that Aisha you would you based on the session that we having now you’ll be able to even improve on what you’ve got am I correct yes sir absolutely oh okay now moving on moving on to how you create relationship so this
Is how you first of all create um based on each of the modeles that you have identified you identify and you put them on um just like here we identify some of these tables and then we are picking them one after the other now let’s look
At the roles now uh we are not keeping user type in a particular table it could have been kept in a particular table and then we reference it and I guess it’s also similar to what um zua was saying that time so if you look at something
That are exhaustive if the list is exhaustive right like uh it cannot be more than this certain number it cannot be more than five you don’t want to create a a special um table for them because you know the list are exhaustive it can only be three patient therapist at me you
Know them this can be known but if the list cannot be known just like row now you cannot guess ahead how many rules you would have and you want to create factivity of users creating as many roles as possible and they can assign that to any user and that is why you are
Creating a separate table for it if the roles that you in your specific application is just going to be certain number of known roles and it’s not going to be more than that going forward you can keep it as what we call and you will
Know it later on as an enom which can be kept in just in an in a string as a as a string of an array in a particular um configuration file server file it will be kept in there so and then people can use so that what
We’re doing this is what we are doing with SP therapies and these things we’re not keeping it uh creating a separate table for user types because we know that user types are they are known and they’re not going to change significantly from this they are not going to change substant they
Are not even going to change at all patient therapies and this like taap for instance you look at T scenario that we painted also you have you have fellows you have Coach you have uh uh mentors you know all those types we know them you know so if you can identify them and
You know in the next 10 years 20 years it’s going to stay this way and you can just keep it like that you don’t have to create table for it but in this case of Ro we we can have as many RS as possible depending on which applications that
You’re having and maybe you cannot know it ahead if they can be known ahead and yeah it’s not going to change substantially also you can keep it as a static array that you can just expose to the front end and then assign just like we assigning it here patient therapies
Otherwise we’ll be referencing it as an ID so now let’s say we want to keep rows let me let me Zoom this in a bit so we can all see what we are talking about so if we have rowes like this uh now who can tell us the
Properties that we want to keep about row idea ID and what R name Ro name Des thank you R name is it because of because of the fact that you watch it in the other video or because that you know you watch and understood what is about R name and what yes Ro description who doesn’t who
Doesn’t understand user ID user ID Hor okay this inside the roll this is r that we are creating now Z sir so your screen is Frozen it’s frozen can you guys hear me now it’s moving now it’s moving IA said um user ID so I was asking said user ID yes this is this is table this is Rose
Table this is Rose so is is it correct to put user ID here I want to understand I’m not saying it’s wrong or right the reason why I put user ID there so that we can be able to link the user to the role that they are performing okay now
Look at it user um um uh AA so if you put user ID here right if you put user ID here you know this is called Road table right what does it mean what does what what what are we saying when we say this is rule this is where we are creating
The various rules right yes so if you for instance if you for instance say if you for instance say that you you want to run it just like we did the other one so let’s say we want to run it you have something like this let’s say you’ve got something like
This you you are you created ID you created row name you created row description and then you created the user ID I’m saying for instance right so if you come here you say this is R name one you call this one for instance for
Instance so you say R name is give us an example of of R depending this is your your own application manager this is your application that has related to drive you call it project manager right yes so let’s say this is the name of a row project manager so manages all the
Projects All Tribe related projects now assuming you assign that to this user uh this user which is an admin user user three assuming you you assign it to the user right user three yes I are you listening now if you want to if you want to assign if you want to assign this
Same role this same project manager to another user how would you do it if another user want to you want you have about two or three project manager I would you be able to assign project manager to because as you are creating this role you assigning it to this
User now if you need to assign another user as a project manager how would you do do it it’s not possible it’s it’s not possible you understand because you you did this right so that is why it is wrong to do to do it like this this is
Wrong this is wrong so if you delete this column here this is wrong only thing that you need here the other stuff that you need are just meta data of date created created by created by last modify modify by all those ones are just metadata to be able
To track the this thing here so when you are creating a role roles are just roles you don’t assign them to anybody as they just stand alone they just stand alone just like when you have a user like this user is just standing alone and then you
Can then begin to assign users to certain things later on so you have like this this is um a row name a row description you can have another row uh maybe you call it patient manager patient manager uh manages the first uh of patients let’s say you have another one
Called uh super ad me manages responsible for everything on the system sorry on the system now you can create as many row continue to create as many row as possible now I mentioned earlier and I’m going to stress it again depending on your application use case if it is
Possible that someone can be a project manager and can also be a patient manager at the same time it means that one that user can have multiple role at the same time what you are going to implement will be a one to many relationship or you you say many to many
Relationship many to many relationship in the sense that if a project manager can be assigned to multiple users and multiple users can also be a project manager that is M many many to many more than one user can be a project manager more than one user can be a
Project manager right so you can assign more than one user to project manager right so that is from from the user side many user to one um roow type and then maybe a user can also have multiple rows multiple rows can be assigned to a user a user
Can assign can get multiple can be assigned to multiple rule that is many to many and I will explain that again so if I come in here and I put if I want to design it as one to one relationship I will come here and I I
Say I would add inside the users table we would add R ID if we add rle ID then here you are going to have something like this so if you insert um another column to the right let’s say we have row ID now look at the row that we have look
At the rows that we have one two three one is one is project manager management sorry project manager second is patient manager super mean you can have as many other rows um so if we come here and we say this person is Row one
This person is r two r one r one all of them yes okay so um just to make sure that I understand the reason why um we are creating the road table is one to many right so we are going to be assigning it to each user rather than putting the
User ID inside the road table right you said the reason we are the reason we are doing what so the road table that we created that one is one to many right table have more than one room no no no the road table is standing alone irrespective of whether it’s uh one to
Many or many to many it doesn’t matter this road table reason we are having a separate Road table is because there can be as many roles as possible that’s why we have this role there can be as many role as possible and we cannot at creation of the role assign it to a
Particular user you cannot as as you are inside this row table like this you cannot put any user nobody has an explicit entitlement to this row whatever you are putting here is a property of that row whatever you put in here in this row table like this a property of the RO the
RO name that’s the name of the RO this one describ the RO describes what date the RO was created and who created it now you cannot put a a user ID straight up like that on this R when you do that it means that that user has an exclusive right to that
Role alone and that user alone have you cannot give that rule to any other user again that’s why we are keeping everything here is just Ro now if we want to assign this R to a user we have several ways of assigning it depending on our policy is either that we are
Assigning is either that a user can only have one role or a user can have as many roles as possible if a user can only have one row that is one to one and then that role that Ro ID will be inside the users’s table and not the other way
Around AA do you understand yes I get you now thank you very much sir okay the more we go uh we we dive deeper the more you you guys will understand just keep it simple now so I’m saying that if it is only one role to one user then you are
Going to create a ro ID here and then you assign it like like this so what we are seeing here is that all of these people are all project manager all of them because this they having all ID 111 all of them are all project manager
Because that is um the RO the RO ID one is a project manager if you change this guy to two and the other one one one you’re saying that the user two is a patient manager and every other user every other users are this this one you have to
Create uh something like this in your head when you are starting up or you you doent it so that you know how it will be represented in the database um later because this is how all those things we designing would eventually turn to so you have something like that something
Like um um this this is one one user to one row one user to one row but if it is possible that a user can have multiple role then you are not going to keep it inside that place what you would do then would be to have a table like this
To have a resolver is to have a resolver called users a like a pivot table users to rows so this is a junction something that joins users and Ro together users and Ro together now you’re not going to repeat what you have inside users and you’re
Not going to repeat what you have inside rows but rather you reference them so when you have users role which is user assignment of roles what you have here would be recording stopped you have its own ID you have user ID that comes from user table and then you have row ID row ID that comes from the row table you know you have user ID this user ID here is equivalent to the ID of the user this one that you have here and then the RO ID is equivalent to the ID of the role that you you’ve got in there
So both of them coming together uh forms this this table here which effectively allows multiple assignment of roles to multiple users and the same user can have multiple roles let’s see what how this works out if you if you if you if you create a visual of it because some
Of us as we are St up you may be struggling to relate to structures like this but you should find it easy when you create it as a table and then try to relate to it if you create something like this for instance you can have ID and you have user ID
And then you have the RO ID just for example now let’s say we have one a user ID if you go into the user table we have number one Isa so if we have a user one with row with Row one it mean zua is a project
Manager this same zubida which is one can also have row two so you can see zua is not having multiple rows zua is of row onea is also r two if you see number three zua is still One recording in progress zua is Row three so this same zuider this same
User of the same user ID having different rows you can see it here like that then you can have again maybe number four is user three having row two user three is Victor and row two is patient manager it means Victor is a patient manager right um this is just an example
For us to make sense of it you know what you have done here is we’ve created a what we call pivot table which is a resolver of um users and role and what you have done here is that a single user can have multiple role and
You can see this row here two has been assigned to multiple user it was assigned to zua and this same two is now assigned to Victor so what we are seeing here is that the same role has been as assumed by multiple users and the same users can have multiple roles that is
Many to many Rel relationship a user can have multiple role multiple role can be assigned to multiple users you understand so if you look at some of the questions that you you you ask me here if you look at it where is it where you when we talked about roles
And user type one to many many to many uh I I think with couple of things I’ve mentioned here you should be able to resolve um resolve this if there are more questions please don’t hesitate to ask so this relationship that we created here is called many to many relationship
You know on one side is one to many on the other side is uh recording stopped right so but what we got here is call many many to many relationship many user having multiple roles multiple roles being assigned to multiple users um right now when you are designing recording in progress when you
Are designing your system when you’re designing your system this details that you have taken here you you are not going to take it in in one in one uh on one screen all this all these details you taking otherwise people would run away from signing up in your application
If somebody is signing up you you’re asking them for too much um you only ask for details that are very critical and important and and important for you to set up the base um profile of that user for instance uh you know so you don’t want
To ask for profile image as I’m signing up you know you can defile certain information and ask them for them later you can def certain information ask for them later and you don’t have to ask please do not ask user to tell you their type of user you cannot ask users I’ve seen
Application someone just we inherited one application one application from someone who was and um when we saw it the way it was designed my boys who graduated from thail Lab were just laughing and you see all this kind of applications everywhere in fact I saw one with Ministry of communication
When they asking users to tell to users to tell them the day that user created see this created created by all this ones are like that are will be supplied underground by the system nobody will fill a form and be saying and be filling dates this will be
Supply Underground by the system the system know them by default this user type too you’re going to have a strategy that is supplied without asking users for it one of the strategy is by maybe the button that the user clicks when they are creating signning up when they’re creating an account where this
They creates uh with they click on patient registration um so when they click on patient registration you already know that they are patient and then you pass in their user type on the ground without asking them to pick whether they patients whether they prist or whether
They are admit you know it it creates some awkward feeling if an experienced developer is feeling such form you know I haven’t said that um so I’m trying to clarify what you take so you you you decide what you want to take um initially that are very crucial
For your application to function things like username password uh maybe first name and last name and email address you want to take that first later as user go comes into the system you then ask them to complete to their profile um so that they can continue but you know that you
Already have their details in the applications and you have something to follow uh with them with uh follow up with them with but if you’re asking them to fill almost everything that you need at the time then uh you’re going to lose so much users than you gain all right so
You can see this is just one entity that we have worked with one entity let me say two entities users and row entity then you’re going to have to move to another entity and then you begin to um expand on it and this user that we worked with is relevant to
All um projects it’s relevant to up to project but different projects will have different user type some use some project will have a single type of users or two type of users or three type of users or four type of users depending on the context of your project you know please any
Question so far because we are going to um you know yes please okay so um you know we have different user types um the since it is relative to all this user table is relative to all um user type yes but there are things missing does that mean
That we are going to have an entity where we keep the remaining details needed thank you very much thank you very much for instance now for doctors you may you will still need to have doctor’s table but the difference from this design or P or therapist table the
Differ from this design from the original one that we started up with where we’re keeping first name first name is this the difference will just be that when we create let’s say we create uh therapist therapist uh table we are not to keep everything that we are already kept in the users table
All all we need would just be a donation of user ID so we say user ID for instance we will have user ID which tells us everything about that that doctor the user’s profile his first name his last name and email address so we’re not going to keep that again here
This guy represent all of that the next thing we want to keep is his specialty because we cannot keep specialty in this table because not all users have specialty we cannot keep medical conditions here because not all users have medical conditions you know this medical condition is specific to type of
Users all right so but what is common to all of them is what we are keeping in here what is specific to them are kept specifics so here I’m going to have teras um user ID which you donate everything about the user and then maybe the is specialization spe specialization
Specialization if you use a z or all right you can have that now even the specialization Al as well uh would have to be a reference because you can have several specializations on the system um say this this this and that but since we are all talking about this in their
Own system they are talking about mental health so it’s going to be people who are Neuroscience or neuro uh yeah uh neurologists or neuros surgeon that psych uh psychotic stuff like that so people that have to do with uh neuro Neuroscience so so you can have specialization here
Right so this specializations can also be a table in in itself where we would document several specializations and then what we just referencing here will be specialization ID you understand it means that a therapist this design you should already understand that a therapist can only one specialty if you
Do it like this if a therapist can have multiple specialty then we’re going to create something like we created for for this Ro ID something like this if is possible that a a therapist have multiple this but most of the times especially if is a standard system they only specialized in
One thing and that thing alone and so you have it like that uh specialization ID uh you can have that and then uh maybe qualification as well the university they attended University they attended uh or education information now if you are putting education information also you realize that a therapist might
Have attended several institutions so that one too will be resolved in another table so you see the table will keep growing like that depending on your design uh need but to answer zua straight you are not going to keep what is specific to each of these
User type in a separate table and some of them would also have have to expand more depending on the type of data some of them will have to be in a separate table and then you are referencing just their IDs some of them will have to be
Many to many some of them will have to be one to many some of them will be one to one does that make sense a bit yes lot yeah and just like any other entity it has its primary key right yes so what we got here is if this guy here
Would have his own primary key thank you very much for that Z so this one here will have it own ID this ID here because I haven’t said anything like that is a PK is a primary key is not Mr Peno this is PK that’s the primary key
Which is a unique primary identifier of this record this guy here is a foreigner in this case recording stopped is a foreigner is a foreign key because it’s coming from users table you know is donated from users table so it’s a foreign key here this one too will be a
Foreign key which is coming from the specialization table so each of them will have their own PK uh this guy here this is the PK here and it makes sense for you to in the PKS the PK should be IDs don’t call them user ID in their own table but you
Call them in in the reference table where you reference them you then call them their name and then with the ID don’t come inside row table and be calling in the row table don’t come here and be saying row ID it should be ID here but inside that another table where you
Referencing row that’s when you call it row ID the same thing with users in his table you call it ID in another table that using it you call it user ID just like we’ve done here so these are best practices and this is this is what you
Want to do some all these things we mentioned are what we already documented in the video that I shared with you but this one is now specifically for your own set you understand and talking to your project so based on what we have design what we have discussed now I want
Each of the groups to ask specific questions as it relates to their own maybe we want to know based on your project what are the user type that you’ve got so I I I would want to anti that questions and um clarify because after now you guys are going to go and
Create ERD for your respective project for us to review so if you want to ask questions based on your own project what we think the user type should be or things that are specific to your project you want to ask the questions time is now yes sir yes good afternoon good
Afternoon Mr Yu thank you very much as regard uhp yes so we be having so a user can be a lender or a borrower MH and then so we we have admin admin user too exactly so that’s the Yes But now but but you have to also be careful
In your own case in your own case right excuse me you you you need to be careful just like if you look at uba the case of uba you know that uba we that we are Huber customer we can also be Uber driver you know that
Right yes so in your own application too you have to decide because you A lender you can also borrow on the platform is that right yes yes so A lender can borrow a borrower can Lear on the platform all right so you have to uh decide clearly what how you are
Because now what if I’m both I’m A lender and also a borrower how do you resolve that how who resolve their own is that they don’t complicate things they have different applications for the two users they don’t use the same application so if a driver you use Huber
Drive you use an application that has been designed for only drivers so if you are also um Huber customer like you want to go somewhere you use the normal Huber you understand and like that that way that way they they don’t mix it but in your own application you don’t want to
Build two two different system you want to use the same system and then you don’t you want to be able to recognize uh to be recognized as such so in your own case you have to use the type very um carefully since a use user
Can be a lender and a borrower at the same time so BBE what you want to do is that you have admin user are we together you have admin user yes sir and then you have every other user type as users whether you’re a lender or your borrower you understand whether you’re a
Borrower or you’re a lender you you’re a user you’re an ordinary user maybe you are categorized as an ordinary user so in your own platform on your dashboard as a user you have an Avenue to uh a button or action to borrow and you equally have an action so we are not
Maybe you are not really separating uh borrower from uh lender per but what you can also what you can have see what you can have is you can have what we call um category and have people subscribe to the category as they want so they can subscribe to lender
Category and borrower category why I said that is that because when someone try to borrow uh on the platform you are supposed to send notifications to people who have indicated interest in lending you understand so indicating interest in lending it just means that you subscribing to lender category so people
Who have subscribe to that it’s just like you going to a Blog uh platform and then you subscribe to different type of content content uh specific type of content so such that when they create such content you get notification about such content being created so this is how yours will be handled not
Specifically um as lender or borrower type do you understand what I mean have I it looks like I’ve confused you can you guys hear me yes we can hear you yes we can hear you doesn’t make sense a bit to you youu is not talking hello sir I have Samson go
Ahead okay um how about if we have something like this like um from the user rules we can see have them like um borrower and lender but we have a button on the dashboard whereby you can click on switch to borrower the moment you switch to a borrower maybe automatic or
Dynamically switch the user R to two for it is using to repr borrower and you want to switch back to lender we say the Buton should return you back to one like um this um 55 case study whereby a seller can be a a a buyer I don’t know I
Don’t know that will work I um uh that works now but your you know what you are designing here is the background that makes that possible whatever you you design here this is theem that you design whatever you have designed here is what will make that switching
Possible now so if what you want to do is that switching of switching uh from borrower to lender hello can you guys hear me yeah we can hear you sir yes we can hear you yes so uh as I was saying whatever you design here is what what makes that switching possible
Now look at it here if you if you are handling them as user types right and then they can switch user type as this things so each time they switch what you are doing is you want to update their their type as this thing that won’t work that won’t work
Even if you you do it like that it works but eventually you’ll see that your application has a very um fundamental problem it has a fundamental problem in the sense that when you switch at that time that user is a blender and is no longer a borrower at
All that’s what you are saying if you keep it like user type if you if you switch you have updated that user to to borrow anything that happens to his other type of user he would be left he won’t be aware of it imagine let’s look at Huber for instance let’s look at
Let’s use a case of huba that all of you can relate to you have Uber drive and Uber uh customer let’s say a user is a Hu driver and is also Uber customer now if he if he’s using the application as a driver if using the application as a
Driver or if he using the application as a customer anything any notification that you will have for all drivers that you send during that time you should also get it let’s say that notification is for all drivers because he also a driver you should also get it
But if you if you switch him and what you switch him what you are doing in the background is that you are updating his Visa type to uh this thing it means that at that time he’s not going to receive the notification that I sent to all drivers
Because at that time is no longer a driver but what we are saying is that you want to create a system just like you have mentioned Samsung that it’s possible to switch to switch type but when each time you switch type you do not lose other type that is turned off um
Currently or you don’t even have to turn off one row one type for the other one you don’t have to turn off one for one you can be a driver and a and a a lender and a borrower at the same time all you
Have to all you need to do is to just indic interest of Being A lender and being a borrower and the system recognizes you as both do you understand what I’m saying yes sir very clear very clear sir yes hello sir yes hello sir yes I’m with
You so my concern is that when we are doing this uh database design we have to consider the the front end the structure yes you have to look at the you have to see database design is the system you you think of the system from a to zed
When by the time you are done designing your database you already know how your application will be built and you will then be guiding your front end you’ll be developing based on it and guiding your front end as as as to what you have designed yes but well in this case we
Have done some designs on the front end so I think according to the front end design so uh we have a different dashboard for a lender a different dashboard for a borer so I think at the point of registration a user have to like choose his account type maybe he
Registering as a vendor or as a borrower so I think we already we already have that design on the front end so now on the back end now when you are saying that uh we can like the account type user type like we we should be careful
Like how do I put this part like we can have let’s say A lender can also be a borrower and a borrower can also be a lender can you hear me sir yes I can hear you and so I’m trying to to think like how how can we resolve that issue
Because it’s not flowing with the front end design anymore yes so front end does not take for back end back end DET take for front end so that’s the first thing because you are the one that is designing the the developing the system they are designing what you have
Developed so the fact that front end has done something wrong back end doesn’t have to follow that you have to look at the goal of your system the goal superate sometimes if you have an experienced person in the fr end it can also guide the back end as to what the
Need and all of those things but what’s guiding both front end and back end is the overall goal of the application and what you gain when you when you implement certain policy and what you lose when you implement certain policy you have to look at what you do why
You’re doing what you’re doing now it’s not like it’s bad to say that um you can only borrow but you have to look at why are we doing that it’s not bad to say that you can only learn it’s not you have to look at what
You’re doing so you have to look at is that what we really want to build irrespective of whether the front end already has one One dashboard or not like that if it is wrong it is wrong there’s no two name for it and it has to
Be done right now what you have right now is that when a user is signing up they indicate their interest recording in progress they indicate their interest AB initial that they are signing up as a as a as a lender and it’s not wrong so this is the policy of your
System it means that if they want to sign up as a borrower again they will create another account as a borrower and then they can use it like that you understand and then they can use it like that that is a an implementation but you have to then sit
On the table and have a conversation of okay what do we stand to gain and what do we stand to lose B based on this implementation right is it really possible for a lender to be a borrower and a borrower To Be A lender look at
What we’re saying is that if you look at this applications let me open I think I have an application here I can use to I can use to explain certain implementation that we we are talking about recording stopped so let me explain this with what you are
Saying and just to subate that it’s not like it’s entirely wrong to have such look at this thing now um this is similar to tries um application recording in progress so you see a when when is someone is creating an account on this on this platform they they are they
Explicit when you’re signning up you either sign up as a patient you sign up as head care provider in this in this case just like a doctor or you sign up as a clinic like an like an Hospital owner you know sign up with a clinic or
Sign up as a clinic you understand so we are very clear as to when you’re signing up the type of users that you are this is because it’s very rare for patient for doctors to also use the same system to even if they are sick it very rare even if a doctor is
Sick the doctor may not use this system so it’s very rare for a doctor to also be a patient on the platform so it’s very it’s going to even if it’s going to happen it’s going to be infinitesimal and that is why he can be we can be sure
As to separating them like that as as as the type um as signning up we understand but in the case of pp it is very very almost 40 or 5050 50/50 as to whether you want to be a lender and you can also borrow on the platform it’s possible everybody even Dango still
Borrows you understand even Dango still borrows you understand and dang still you know give a lot of people money so if you look at the your own context you see that it is very likely that a user might want to use the platform to borrow then how easy are you making it possible
For them because I have only one user and I that my my usern name is Kenny at whatever.com and then because I want to borrow you ask me to go and create another account and have that as borrow and if I want to borrow I will log out
Of my lender account and loging into my uh into my borrower account and vice versa I I will do that you understand and you don’t forget your design here has captured them as a user it means that and username has to be unique so it means that this person is going to have
Two usernames because he a two is is of two user types because once this person is already a user um is already um what’s it call all this person is already registered on the platform a username should not should be unique another thing that can be unique
Is email uh so because this guy want to be a borrower and lender you want him to create two accounts two account on the platform so and if you want to use one you has to log out of the other one so you see that even you running that in
Your head you see that you’re already creating complications for the user so your user will find it difficult to use your applications as such all right so what you can do then is to have them like all users all users can borrow and all users can
Lend all users can borrow all users can learn all right so now if you want to borrow you want to borrow more you know if you want to do it like all users can borrow and all can learn then you can just put tag them create like uh
Um user tag if they have borrowed if I’ve ever borrowed or they have not borrowed or you want to just create a uh a way of identifying this person as a borrower just this is where Samsung’s implementation will now come in so on the front end you can ask them um switch
As borrower and lender you understand they can switch as borrower and lender so when they switch that’s your dashboard that you already create when they switch as lender what you are showing them will then be functions that are related to lend up not like you are
Logging them out or logging them in you just show them you switch so that you can show them dashboard as it relates to lender and then when they switch again you show them last but you are not switching their user type because they can borrow and lend so there’s no us
There’s no lender there’s no borrower but when you when they switch You’re just showing them things as as uh relates to the functions that they they about to perform do you get what I’m saying so design requires a lot of thought process you have to look at the
Decision you are making why you are making it what do you stand to gain what you stand to lose lose how does it contribute to the um user friendliness of the application you know or the complexity of the application does it make sense a bit
Youu yes sir yes sir made a lot of sense oh okay thank you very much you’re welcome sir I have a question go ahead okay sir so uh our app be be um B medics okay so our main target is hospital but then the hospital can now
Have ad patient doctor and staff that may have um um just limited admin admin right so that they can onboard new patient so in this scenario how how how are we going to um categorize our user type and also are we going to have a specific design for hospitals
Because it’s going it’s our main target are hospitals so different hospital are going to use our our yeah so are you going to have different design for hospital what do you mean by that are you going to have a table um yes table yes sir definitely definitely you’re going to have a table
For for hospitals you’re going to have a table for hospitals because hospitals is not the same as users then hospital will have user Hospital each of these Hospital would then have users so let’s say you have Hospital come before user Hospital comes before user because each of these user belong to a
Particular Hospital right so and then you then also want to decide is it possible for a user to belong to multiple hospital or to One hospital we mentioned it that time we said what maybe what we want to do now right now is just a single user to a
Single um to a single hospital for instance if are a doctor you only work in a particular hospital if a patient you only um your records are only in this hospital we don’t want to transfer records in this hospital to another records in another hospital except the
Patient want it so and that can be resolved later on so as we’re growing since you’re building and this is pretty much your first Enterprise project we start it simple and build up you understand so now you are going to have in your own case you have hospital and with Hospital name
Hospital um description Hospital address phone number you know the location State and all of those things like that that the hospital is um like that and then you then have users of that hospital so it means that in the users profile uh in your own case you will have Hospital ID
Which enables you to resolve users because when a particular Hospital logs in they are supposed to see only users of their own hospital they cannot see other users of other hospital so at the back end you are able to get by hospital um so they going to there’s going to be
Something like Hospital ID as a foreign key here which recognizes the hospital that that user belongs then beyond the hospital uh ID which separates Hospital uh users of hospital from the other then you then go to level of the type of users in that hospital now when you get
To the hospital um just like you have mentioned they are patients they are doctors and they admin then this user type like we have it here because your own project is very related to trive it’s just a couple of because trive in essence is a subset of your own
Application trive is a subset what trive is doing is um the the workflow of what will be done within the hospital consultations and all those things like that you know so um these users here are essentially the same users of your own application uh is that
Is either that user is a patient is either that that user is a doctor or that user is an admin uh user which would then have role um an admin user will then have role so maybe you want to give a different role to all users and call it
User you know and then admin users will have different roles with different powers is it making any sense to you yes sir Yeah so basically that so there will be Hospital ID which separates One hospital from the other and each of these users would have type patient doctor ad meit
Like that please everybody I need to you you want to ask further question should no Sir please who else want to ask question as regards to their project after now you are going to work on your own sir yes creating ERD ask questions um I want to talk about inoc connect yes in know connect is actually um a job placement and and career
Mentorship Support app so okay um our user type we are mentors and mentees okay so we also have um a kind of a section whereby someone can use the app and like post a job like a job um like an employer can can post a job and also someone can also
Like come to the place and also seek for like um an employee so so that’s um like a um user that type you said on your platform is inoc conect yes like that’s um post jobs right yes yes like is a career um is a mentorship um H and also people can also
Come there and find jobs and then um employers can also post their jobs there like people looking for okay great certain kind of okay so then can you can you resolve it with yourself if you want do you what do you want do you want people who post job
To also apply for jobs is it is it possible yeah want it to be very Dynamic kind of like people can also does it make sense does it make sense for like let’s say you know those are posting jobs are pretty much like uh employers right
Yes sir ahuh so they said they sign up as like a company is it though initially anybody can just sign in we don’t didn’t really categorize whether you’re signing in as a job owner but there’s actually a section which you can go to then that
Section you is just for you to post a job then you can go to that section and either post like post a job then find a job too in that section okay so you can post a job and also find a job yourself yes on that section okay is that is
That when you that when you go to that section is actually called an um employer like it’s called an employ there’s an employer account that will made in that section okay kind of so then you probably create an account okay then including your company’s name like
Um the number of employees then okay you canot continue to um impute the roles that you are looking for okay and then you you end up with the the sign up then you can now post the job there oh okay okay so basically um a user you want a user to be able
To uh post um roles jobs when they have one and yes this same user can also see a role that is interested in and then the user can apply apply right yes sir the user can apply so uh so your your case is pretty pretty similar to the case of
Pip um it’s pretty similar to the case of py so but what you’re going to do in your own case is that um when you when you log in as a user you actually logging them in as a user since they can uh they can post job and they
Can uh they can post job and when you’re posting job there’s no specific thing that is required not paying any money to post job do you no sir we no sir okay you didn’t include that and and that that is not part of your your scope for now right
And when you job too you are not uh you are not posting you are not paying anything to apply for the job yes sir right yes sir you’re not paying it’s just for you to so yes so but basically what you will do is very
Similar to um what PDP you are going to do you have um users being able to subscribe to a job category uh and what I mean by that is the best way to to handle it so that people can uh get jobs notifications of jobs as you relat to them for instance
If um if um Victor is an employer on the platform and I a is a jump finder on the platform when when Victor post a job that Aisha is interested in AA doesn’t have to come to the platform to know that the job a job has been created in our
Interest you you know she doesn’t have to always come to the platform and be checking what job has been created what makes the platform interesting will be as soon as Victor post a job that I I she is interested in Aisha get a notification that the job has been
Posted and we shouldn’t bother Aisha all the time even if each time a job is created irrespective of whether she’s interested or not so when a user logs into the application you want the user to be able to um select their interest maybe software the type of role they are
Looking for software developer uh so you’re laging it’s not I’m lagging yes the network is is a network or hello is it better now yes sir it’s better now so you get what I’m saying so when the user logs into the platform you want the user to be able
To to be able to uh specify the type of roles they are looking for the categories of role development software developer something like that such that when any job is posted in that category they get U notified of it okay so that is to say that they’re interested in um getting
Jobs like that and when you are showing them jobs you are showing them jobs as it relates to their interest as well okay now similarly then you then have a place where they can just go and create a job that you you two can post jobs you
Know you can have something like that just like hu will tell H when we using Uber that you can also make money you know on Huber so you can also put it there like that when people like you can you to um post jobs so just a Von and
Then the guy can go and post jobs in essence what we are saying is that you don’t have to identify people since they can do both you don’t have to identify them as job poster or job uh job Seeker you know since they can do both so you
Generalize them as users and then you have functionalities of them you know being able to do the the two so your own case you just want to keep them as user do you understand sir and then you have admin type admin user type of course the admin which are the guys who
Are in charge of the system those guys will have their own user type and then every other users are just user make sense does it make sense please I think his Network hello can you guys hear me yes sir you can hear hear you sir I thinkk okay his Network logged
Him out okay yes all right so I’m listening to other others please others please ask your question hello sir I’m raising my hand okay go ahead based on what um Daniel just on the question he asked um for instance we are making we are narrowing the app on
That job search for find a job and then post a job it’s only companies or HRS that will be posting a job on the job search and want to make it real not that anybody can come and post a job and then it should be like it not be like a
Um I mean it will not be like a good platform whereby you’ll be saying fake jobs so people will like want to leave the platform so that’s I want to stand out like that so whatever company that is um posting a job will be verified
First by the Admin and then um you can post jobs and thank you for the notification aspect of it it would be like something we’re going to add to it and then to make money we thought of trying to um act as n also that um the
Train mes and then companies come to um them and then get this mes because on our platform they would have just um reduced the recruiters way of carrying out all this job inter VI and then the excessive money they pay and things like that waste time so would have done that
Through the processes we have so we plan on making money by standing as consultants to these um companies that register under us so that’s part of it again so if you want to now carry out such um on our database in a simplified form first before we now go into um details
Later all okay okay yes I I I get what you mean so but now what you are saying in essence is that you want hro HR people who are recognized as HR to be the only type of users that can post jobs not just na coming to post job
Not just V to post job not just R person coming to post jobs then if if that is the case then you have to you you need to separate the type of users so it’s it’s very unlikely for an HR to also be looking for jobs if that is the case
That’s why I’m saying that you have to know what you are building if that is the case you have to separate the user type and again you don’t there has to be verification process to ensure that this person is actually um a recognized HR so you may want to have some documentations that
The person present to ensure that you know you get um you verify so that you use that to verify the the the patient U sorry the user uh as to who they claim they are so if you really want to do go that route so you
Have uh sign up as HR or a recruiter and sign up as you know a job Seeker so you have two different distinct sign of types and then you know you are able to separate them uh decently and like that and like I mentioned there has to be something that
You ask them to upload that the admin will see and ensure that um they are really uh they are not uh someone masquerading as as HR you get what I mean so yes sir can we also use companies too yeah yeah you can call it company you can call it HR whatever name
You want to call it you call it just have but of course there has to be uh verification process like I mentioned does that make sense please any other question please ask okay so in the absence of further questions so there are couple of these
Things I didn’t record but I I think I I I recorded uh um the majority distance so since we are in the same group um if there are further questions that pop up even as you design your ERD feel free to to drop it in the group so
Either anybody can answer it or I can you know clarify it for you um so your exercise is to then design the ERD for your project so for each of the groups um you come together those of you in the same group and design the ERD for your respective project
Comprehensive one um be ready to to explain and defend any property that you put and why you are putting it in there when you design something as one onone you want to tell us why you doing it as one one one to one if you do it as one
To many or many to many you want to tell us why you did it as many to many so uh please you have um today and tomorrow to do that comprehensive design of your ERG right and you you submit it um by the close of business tomorrow to be
Reviewed all by all of us together on Wednesday sir thank you you’re welcome thank you thank you sir well done guys have a good day everybody
Video Keywords: Database Design & Development, [vid_tags]
-
Sale!
Wireless WIFI Repeater Extender Amplifier Booster 300Mbps
$29.99$14.99 Add to cartWireless WIFI Repeater Extender Amplifier Booster 300Mbps
Categories: Electronics, Wi-Fi Router, Wireless Wi-Fi Extender Tags: 300Mbps, 802.11N, Amplifier, Booster, Extender, mobile wi-fi booster, Remote, WIFI, Wireless, Wireless WIFI, Wireless WIFI Repeater, Wireless WIFI Repeater Extender, Wireless WIFI Repeater Extender Amplifier, Wireless WIFI Repeater Extender Amplifier Booster, Wireless WIFI Repeater Extender Amplifier Booster 300Mbps$29.99$14.99 -
Sale!
Full RGB Light Design Gaming Headset Headphones with Mic
$24.99$14.99 Add to cartFull RGB Light Design Gaming Headset Headphones with Mic
Categories: Electronics, Gaming, Gaming Headsets Tags: Design, Full, Full RGB Light Design Gaming Headset, Full RGB Light Design Gaming Headset Headphones, Full RGB Light Design Gaming Headset Headphones with Mic, Gamer, Gaming, Gaming Headset Headphones, gaming headset wireless, Headphone, Headphones, Headset, Light, Mic, Package, RGB$24.99$14.99 -
Sale!
Wireless BlueTooth Multi-Device Keyboard Mouse Combo
$39.99$19.99 Add to cartWireless BlueTooth Multi-Device Keyboard Mouse Combo
Categories: Electronics, Gaming, Gaming Keyboards, Keyboard Mouse Combos Tags: Combo, Keyboard, keyboard mouse combos, Mouse, MultiDevice, Set, WireKeyboard Mouse Combo, Wireless, Wireless BlueTooth Keyboard Mouse Combo, Wireless BlueTooth Keyboard Mouse Combos, Wireless BlueTooth Multi-Device Keyboard Mouse Combo, Wireless BlueTooth Multi-Device Keyboard Mouse Combos$39.99$19.99 -
Sale!
High Back Leather Executive Adjustable Swivel Gaming Chair with Headrest and Lumbar
$199.99$139.99 Add to cartHigh Back Leather Executive Adjustable Swivel Gaming Chair with Headrest and Lumbar
Categories: Gaming, Gaming Chairs Tags: Adjustable, Chair, computer chairs, Desk, Executive, Gaming, Girl, Headrest, High, High Back Leather Executive Adjustable Swivel Gaming Chair, High Back Leather Executive Adjustable Swivel Gaming Chair with Headrest, High Back Leather Executive Adjustable Swivel Gaming Chair with Headrest and Lumbar, High Back Leather Executive Adjustable Swivel Gaming Chairs, Leather, Lumbar, Office, Racing, Swivel$199.99$139.99 -
Sale!
Professional LED Light Wired Gaming Headphones with Noise Cancelling Microphone
$29.99$19.99 Select optionsProfessional LED Light Wired Gaming Headphones with Noise Cancelling Microphone
SKU: N/A Categories: Electronics, Gaming, Gaming Headsets Tags: Cancelling, Gaming, Gaming Headphones with Noise Cancelling Microphone, gaming headset, Headphones, Headset, LED, Light, Mic, Microphone, Noise, Professional, Professional LED Light Wired Gaming Headphones, Professional LED Light Wired Gaming Headphones with Noise Cancelling Microphone, Wired, Wired Gaming Headphones, Wired Gaming Headphones with Noise Cancelling Microphone$29.99$19.99 -
Sale!
Gaming Desk with LED Lights USB Power Outlets and Charging Ports
$349.99$249.99 Select optionsGaming Desk with LED Lights USB Power Outlets and Charging Ports
SKU: N/A Categories: Computer Desk, Gaming, Gaming Desk Tags: and Charging Ports, Charging, Desk, Desks, Gaming, gaming desk with led lights, Gaming Desks with LED Lights, Home, LED, Lights, Monitor, Office, Outlets, Port, Power, Room, Stand, USB, USB Power Outlets, White, Workstation$349.99$249.99 -
Sale!
Wired Mixed Backlit Anti-Ghosting Gaming Keyboard
$99.99$79.99 Add to cartWired Mixed Backlit Anti-Ghosting Gaming Keyboard
Categories: Electronics, Gaming, Gaming Keyboards Tags: Antighosting, Backlit, Blue, brown, Gaming, Gaming Keyboard, gaming keyboards, gaming keyboards and mouse, Keyboard, Laptop, Switch, Wired, Wired Mixed Backlit Anti-Ghosting Gaming Keyboard, Wired Mixed Backlit Anti-Ghosting Gaming Keyboards, Wired Mixed Backlit Gaming Keyboard$99.99$79.99 -
Sale!
Wireless Bluetooth 5.3 ANC Noise Cancellation Hi-Res Over the Ear Headphones Headset
$119.99$59.99 Add to cartWireless Bluetooth 5.3 ANC Noise Cancellation Hi-Res Over the Ear Headphones Headset
Categories: Electronics, Gaming, Gaming Headsets Tags: 5.3 ANC Noise Cancellation Hi-Res Over the Ear Headphones Headset, ANC, Audio, Bluetooth, Cancellation, Ear, Earphone, gaming headset, Headphones, Headset, Hi-Res Over the Ear Headphones Headset, HiRes, Noise, Wireless, Wireless Bluetooth 5.3 ANC Noise Cancellation Hi-Res Headphones, Wireless Bluetooth 5.3 ANC Noise Cancellation Hi-Res Over the Ear Headphones Headset, Wireless Bluetooth 5.3 ANC Noise Cancellation Hi-Res Over the Ear Headphones Headsets$119.99$59.99 -
Sale!
Wired Sports Gaming Headset Earbuds with Microphone
$19.99$9.99 Select optionsWired Sports Gaming Headset Earbuds with Microphone
SKU: N/A Categories: Gaming, Gaming Headsets Tags: Accessories, Earbud, Earphone, Earphones, Gaming, gaming headset with microphone, Headphones, Headset, IOS, Microphone, Sports, Wired, Wired Sports Gaming Headset Earbuds, Wired Sports Gaming Headset Earbuds with Microphone, Wired Sports Headset Earbuds$19.99$9.99 -
Sale!
150W Universal Multi USB Fast Charger 16 Port MAX Charging Station
$49.99$29.99 Add to cart150W Universal Multi USB Fast Charger 16 Port MAX Charging Station
Categories: Charging Stations, Electronics Tags: 150W, 150W Charging Station, 150W Universal Multi USB Charging Station, 150W Universal Multi USB Fast Charger 16 Port MAX Charging Station, 150W Universal Multi USB Fast Charger 16 Port MAX Charging Stations, 150W Universal Multi USB MAX Charging Station, 16 Port MAX Charging Station, 3.5A, Charger, Charging, Fast, laptop charging stations, Max, Multi, Port, Stand, Station, Universal, USB$49.99$29.99