Student entrepreneur here,
— I'm sorry if some parts are not relevant or incorrectly explained and edited to make sure they match the forum standards. (If my problem is solved, many newcomers can benefit from it.) —
I'm just beginning to learn Database Design. I spend many hours, but I'm still a bit behind schedule, and especially for this job I can not count on anyone on our team, so I come here for advice.
Language: Dart __ SDK: Flutter __ Cloud Service: Backendless __ Concept Modeling Tool: Creative __ Logic Modeling Tool: Oracle SQLDeveloper Database Modeler
Resources: "Learning MySQL" by Hugh E. Williams, Saied M.M. Tahaghoghi
Problem at hand: Parking App users can reserve or offer parking. How do I solve this in the entity relationship diagram? There are no two types of users, except that the use cases dictate that you can "monetize" your parking space in the profile area (like one you own and formally register, not one you've rented through the app). You can use your account continue to use it to reserve parking anywhere in the main cities of Colombia.
((Story / context))
The company I am part of the used Google Cloud service Firebase for authentication (Firebase Auth) and storage (Cloud Firestore). This was integrated into Kotlin and Swift Apps.
We recently introduced Flutter as it accelerated the development process and the versatility of our products. However, it did not come without costs. We have a lot of problems with Firestore and have tried Backendless for a particular project. We are students and since I have another job and sleep 3 REMs per night (4.5 hours), I can not really bring in the kind of MAD 3-day concentration needed to overcome my current obstacles.
Backendless was simply chosen because it integrates easily with Flutter, which my boss simply loves.
I really do NOT know. I am sure that I can continue on this path and provide a working database.
However, I am not sure if this will be the best database or if I am able to handle subsequent problems and scalability, and so on.
I am looking for experienced database administrators and this is the best place I can imagine.
I'm too tired to even really structure that.