3 ms·
I tried to explain this once in an interview and the interviewer was not happy. They didn't like the idea of deploying a dozen different services. They also did
by gravyboat 10y ago
I tried to explain this once in an interview and the interviewer was not happy. They didn't like the idea of deploying a dozen different services. They also didn't like my ideas around keeping the services relatively simple and scaling out as needed. I can say I'm glad I didn't take that job.
- golergka 10y agoTechnical interviews go both ways.
- riffraff 10y agoto be fair, it is quite possible an app does not need a dozen different services, and using them would just introduce unnecessary complexity. E.g. slashdot used to run with, IIRC, only 4 roles: memcached, reverse proxy, apache, and mysql. Your interviewer might have just failed in explaining the problem constraints properly.
- javajosh 10y ago>Your interviewer might have just failed in explaining the problem constraints properly. The simpler and more common explanation is that the interviewer was looking to have his biases reflected by the interviewee. In my experience it is difficult for a certain kind of mind to distinguish between "This person is stupid/crazy/wrong for the job" and "This person knows something I don't".
- hinkley 10y agoHaving the wrong service boundaries can obscure the data flow in ways that can be hard to fix. You end up with high fanout or ugly caching layers where a simpler structure might have been possible before process boundaries were introduced. Best to give it some time, figure out where the important interactions are and separate things that don't interact heavily.