Which do you prefer - a micro-service approach or a monolithic app?

How to Answer
Answer Example

When asking about a preference, the interviewer is seeking to understand how you approach your work. Your response to this question is based on two factors. The first is your experience and skill set in this job. The second is the research you have done about Amazon and your understanding of their preferences for the type of operations they perform. Your answer can either align with Amazon's processes or conflict with them. If you choose to conflict with them, you should be able to rationalize your answer based on your experience.

"While I'm aware that Amazon prefers monolithic applications, I use a micro-service approach. I like to do this because it allows me to create different services that can operate independently and, therefore, more robustly. While this approach results in better performance and more efficient code, it also creates multiple failure points. Extensive testing before putting the application into production can usually mitigate this."

Next Question

How to Answer: Which do you prefer - a micro-service approach or a monolithic app?

Advice and answer examples written specifically for an Amazon job interview.

4. Which do you prefer - a micro-service approach or a monolithic app?

How to Answer

When asking about a preference, the interviewer is seeking to understand how you approach your work. Your response to this question is based on two factors. The first is your experience and skill set in this job. The second is the research you have done about Amazon and your understanding of their preferences for the type of operations they perform. Your answer can either align with Amazon's processes or conflict with them. If you choose to conflict with them, you should be able to rationalize your answer based on your experience.

Answer Example

"While I'm aware that Amazon prefers monolithic applications, I use a micro-service approach. I like to do this because it allows me to create different services that can operate independently and, therefore, more robustly. While this approach results in better performance and more efficient code, it also creates multiple failure points. Extensive testing before putting the application into production can usually mitigate this."

Next Question