What do you usually design first, API or data model(s) during system design? (After clarifying questions and all that jazz)
Whats there to design for api? I only do backend system design and the flow of info..
I do api first because the inputs for that can help determine what you need to store
Data model feels to me so much detail to cover in 40 mins. Api is good, then whole bunch of topics (replication, caching, monitoring, concurrency, analytics etc) if it is not a deep dive question
I am seeing you so much on blind Genesys
If you need to fully flesh out data model, it comes before api. Api semantics should be influenced by the data model, not the other way around.
How can you model any data in NoSQL without knowing their usage?
I guess to revise, this seems highly dependent on the specific scenario presented in the interview setup. But IMO it’s pretty unusual to try to reason about actions before you reason about entities or data
The parameters of the API will define what are the minimum columns you need to have in your DB schema, so API first
Tech Industry
Yesterday
431
Is Sillicon valley dead for good?
Personal Finance
Yesterday
1753
Thank you AAPL and NVDA
Today I Learned
Yesterday
1470
White male privilege is real
World Conflicts
3h
223
Peaceful Protest Hasn’t Worked and Has Been Met With Aggression.
Personal Finance
Yesterday
597
Biden wants to raise capital gains tax to 40%
Doesn’t matter do both