Architecture of larger convex apps.
Hey guys, I'm a solo developer working with Convex and some of my apps are getting bigger with complex business logic. I wanted a cleaner architecture approach but don't want to over-engineer since I'm working solo.
I asked Claude for suggesting and it gave me the ones in the image, but I'm not experienced enough to tell if they are good or not.
Would love to hear from seasoned devs about:
Have you used any of these patterns with Convex?
Which approach would you recommend?
Any pitfalls to watch out for?
1 Reply
One pattern we've seen larger codebases use is splitting up the schema into smaller pieces, and using "accessor" functions to access it
These images don't mean much to me
What are the pain you're you're hitting? Maybe they can be addressed directly or the right pattern will be informed by what's a pain now.