Depends what your product is really about ? What are the customer bases ? Figure out critical featues that customer uses ? Figure out the low hanging fruit and start moving low critical features into different microservices step by step and mean while supporting legacy code bases. If its a huge legacy monilith code and you can to rebuilt a monolith again welcome to the recursive my friend . Lets get back to past when legacy was built again :D
Looks like i needs microservices . What you can do is make a prototype of working microservices feature from existing one show him , it may motivate him to do microservices
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.
Depends what your product is really about ? What are the customer bases ? Figure out critical featues that customer uses ? Figure out the low hanging fruit and start moving low critical features into different microservices step by step and mean while supporting legacy code bases. If its a huge legacy monilith code and you can to rebuilt a monolith again welcome to the recursive my friend . Lets get back to past when legacy was built again :D
It's a huge legacy monolith code :)
My managers don't want to rebuild. If I were them, I would rebuild.
There are critical features like payment, appointment, etc.
There isn't any comment about methods, etc.
Imho, this will be my best work :D
There is a code like that;
Looks like i needs microservices . What you can do is make a prototype of working microservices feature from existing one show him , it may motivate him to do microservices