Thank you
Where do you draw the line when to use SP's or ORM? Considering not everyone understands database in depth and can write performant queries or SP's.
I know its very simple view and probably tons patterns (like CQRS) and infrastructure/serverless/geo-replicated architecture might be use behind the scene.
Have you ever worked on such systems where both ORM and SP's are used and how do they keep logic not fragmented at multiple places at scale?
TLDR; How highly scalable apps manage DB interactions in code vs handwritten SQL?
We are facing completely hopeless situation where no one is providing us any answers or providing support for PAID service.
Can anyone help or provide any clues on how we can talk to actual support team?
So how do you handle such scenarios where you might have to wait till API X-Ratelimit-Reset again after some time and avoid 429 too many requests.
Any such patterns or libraries for handling rate limited api in application.
Also, I'm looking for approximate time and what would you recommend to junior dev or senior dev who are just starting with docker.
Basically i'm looking for some realistic experience with timeline dev would take as my company going start using this technology. I love to hear your thoughts on it.