I'm a software engineer that loves to discuss different architecture choices and the reasons behind them. I enjoy reading architecture blogs and books, especially ones with happy endings.
Keep in mind that a microservice architecture isn't a solution for all problems. So if the amount of work isn't dwarfed by a perceived benefit then don't do it.
My suggestion would be to find out why your employer doesn't want to move to a microservice architecture. Then build a prototype at home using the latest version of the technology stack you use at work and address their concerns. Usually this will mean automating the build and deployment, implementing a strategy for versioning the API, and minimizing the cost of the microservice solution. Then share what you've learned at work. Show that the build, deployment, versioning, cost, and any other concerns are problems you've solved. Make sure you show off some of the features of the latest version of the technology stack that improve your product or simplify engineering. Finally, ask if you can experiment with the next big feature or major rewrite. Then show that the reward was well worth the cost. When that is successful, then with every significant change to the monolith you'll likely have a listening ear on moving that part to a microservice too.
This is an approach I've used for implementing several architectural features in the past that has usually been successful. Let me know if this or any other approach works for you.
I'm focused on developing and expanding my knowledge and skills. Enjoying new challenges. I'm assuming that there are no stupid questions, there are only silly answers.
Thanks for your reply. It sounds like a good plan. I've tried to adopt part of the system but it extremely hard to rewrite after hours at least a small piece of a monolith system based on ca. 7 billion of code lines 😉 I've heard that there is no time for rewriting the system and we have to focus on new feature delivery and bug fixing. Sad but true. Nobody wants to pay for architecture improvements even if they are beneficial from a long-term perspective. I've changed my work a few weeks ago so maybe the new employer will have another view on that. Fingers crossed 😁
BTW I'm aware that the microservice architecture isn't the silver bullet for any kind of solution 😁
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Rafal,
Keep in mind that a microservice architecture isn't a solution for all problems. So if the amount of work isn't dwarfed by a perceived benefit then don't do it.
My suggestion would be to find out why your employer doesn't want to move to a microservice architecture. Then build a prototype at home using the latest version of the technology stack you use at work and address their concerns. Usually this will mean automating the build and deployment, implementing a strategy for versioning the API, and minimizing the cost of the microservice solution. Then share what you've learned at work. Show that the build, deployment, versioning, cost, and any other concerns are problems you've solved. Make sure you show off some of the features of the latest version of the technology stack that improve your product or simplify engineering. Finally, ask if you can experiment with the next big feature or major rewrite. Then show that the reward was well worth the cost. When that is successful, then with every significant change to the monolith you'll likely have a listening ear on moving that part to a microservice too.
This is an approach I've used for implementing several architectural features in the past that has usually been successful. Let me know if this or any other approach works for you.
Good Luck!
Thanks for your reply. It sounds like a good plan. I've tried to adopt part of the system but it extremely hard to rewrite after hours at least a small piece of a monolith system based on ca. 7 billion of code lines 😉 I've heard that there is no time for rewriting the system and we have to focus on new feature delivery and bug fixing. Sad but true. Nobody wants to pay for architecture improvements even if they are beneficial from a long-term perspective. I've changed my work a few weeks ago so maybe the new employer will have another view on that. Fingers crossed 😁
BTW I'm aware that the microservice architecture isn't the silver bullet for any kind of solution 😁