I am working on bubble since 1 year.
Till now i worked on multiple apps (to be precise 4) which are real time deployed live apps…
I often realise that while developing any app i mostly mess up the database design / structure
**mostly it will be fixed by my seniors & sometimes by the experts of this forum like @mikeloc@adamhholmes@Jici **
Can anybody guide me how can i improve this ?
Any recommended book for database structure design / course ?
Off topic, just out of curiosity i would like to know
How did you improve your understanding of databases when you are on intermediate stage of your bubble career ? (I know you are having a lot of experience now but during initial years of your bubble)
@mdburhan3, I’m not sure how much my understanding of databases has improved over the years, but my thinking about how to approach the data types when I start a new Bubble app has definitely evolved.
I’m sure some folks would disagree, but I think it is a waste of time to try to design every aspect of your data types before you start building a Bubble app because no matter how thorough you think you can be, the design is almost certainly going to change as you go. What I try to do is make sure I have all of the big aspects of the design covered up front. For example, does the app need to support multi-tenancy? Are there any data types that look like they will contain a large number of fields, and should I consider creating satellite data types instead of including all of the fields in one data type? Am I setting the data types up in a way that will make it easy to configure privacy rules? Should I use list fields, and if so, will the potential size of any of the lists affect performance? Etc.
Anyway, that’s just my approach… your mileage may vary.
Check out www.nocodedatabases.com - there is a library of prebuild databases that you can copy and paste. Then, you can learn how those DBs were structured as they were created by professionals like myself!