I'm writing a bunch of different codebases, some I might use in the future or open source if I like it enough; I've been having trouble finding answers to questions like:Best practice for multiple/batch querying postgres? Like,create a payment, then create an invoice, then create [x y z]: Should I create separate routes to query separate entities?Is there a certain amount of "one to many" where I should think of using "many to many"?I've seen some very big mistakes happen I can learn from, like huge queries. Where do I begin to avoid that route?What's a proper way of planning, white boarding?I'm more looking for references I can look at (maybe both good and bad?), than typical theoretical advice also. Thanks for any tips!
Submitted January 04, 2017 at 06:25AM by sorry_mother
No comments:
Post a Comment