Internal Service Development

[EdloPosc]

We are planning to develop a system for an internal company service (ticket tracking, user management, and integrations with various external services). The developers suggest building it using modern JavaScript/Node.js with a modular structure and APIs, so that functionality can be easily extended and new services can be integrated later. However, I am not fully sure how justified this approach is in the long term compared to simpler off-the-shelf solutions or a monolithic system. Has anyone worked with something like this, and what is usually chosen at the start, and what should be taken into account?

[LEPALY]

I am strongly against unnecessary complexity why build an overcomplicated system with microservices for a simple admin panel? You will only inflate the maintenance budget, run into deployment issues, and face a lot of bugs in module interactions that will be extremely hard to debug.

[RedJoLak]

You can go in different directions: either use a simpler monolithic system, or build a more flexible modular JavaScript architecture where everything is separated into services and APIs. In the second approach, people often use composable architecture solutions such as systems like https://medusajs.com/ Especially in cases related to nodejs ecommerce. This way, the system is assembled from separate parts and is easier to scale and adapt to different needs, but the development and maintenance complexity is usually higher than with ready-made off-the-shelf solutions.