Are you planning to rebuild your application into microservices only because Netflix has 100s of microservices and they talk very proudly about it, or because you actually have scalability problems that can not be solved in any other way?
This is very common in the current startup world, but guess what, Netflix hasn’t started using microservices for the first 10+ years of its existence, so you should ask yourself: am I just buying into the hype or do I really need this technology?
This can be applied not only to microservices but to any technical challenge that you can read on papers, blog posts or videos from the big companies. If you actually have a problem it’s very good to look at others who reached that scale and solved that problem, but I think any company should keep the technology stack as simple as possible until this simplicity doesn’t scale anymore (and I can guarantee you, any technology scales with no problem up to 1000s of users/requests).
Another very common problem is trying to predict how a complex system will behave in multiple years when you will have exponential growth. Probably you will realize soon that your predictions were wrong, and your implementation is wrong and now you need to change a complex system with live users instead of a simple one. Let’s keep it simple, as much as you can. Every complexity you add when it’s not needed will bite you back later.