- Is an API Gateway always needed?
- Should we always state that we're going to follow microsservices architecture?
- Should we always state which architectural design we're following? (e.g.: MVC, Hexagonal)
- Can we assume something together with the interviewers? Let's say the interviewer asks how many servers are needed, can we answer something like: it depends on how many concurrent requests one server can handle. If we expect 10k concurrent request and each can handle 250 concurrent requests, then we're going to need 10000/250 = 40 servers.
- Is user authentication always talked about when the system involves unique users? If so, is it always the case to show the 'user service' in the design?
- Is it fine to not know right from the beggining if we're going to use NoSQL vs SQL ? And just say: this is the modeling of the entites, but as of now I'm still not sure we should use SQL vs NoSQL or a mix.
Comments (1)