QuickBase Architecture Considerations
So, I'm new to QuickBase, and I'm trying to understand the true intent of this 'codeless' application. I have a complex set of data interactions that I must control, and I'm wondering if I should...
Forum Discussion
If you have complex logic then you have complex logic.
Breaking up that Logic into multiple applications just makes it even more complicated to figure out what is connected to what. . Hence one app is better than multiple apps.
Breaking up that Logic into multiple applications just makes it even more complicated to figure out what is connected to what. . Hence one app is better than multiple apps.
- Thanks for your time. I believe you are right. I guess the only reason to go the microservice route vs monolithic route would be scalability, and I don't think I'll have that concern on this venture. (famous last words..)
I'm going the monolithic way. I'll be happy to let you know how it goes once I'm fully-involved. Also, I'm sure I'll have many questions along the way.
Thank you again for taking time to help us newbies along.
Sincerly,
~Rob - QuickBase will be able to scale to meet the needs of your type of data and we are here to help you get your relationships set up. There are several of us on the Forum who revel in complicated Relationships. .