>essentially keeping on-prem 2000's philosophy and revamp it as microservices)
This sounds like a company that is frozen by it's legacy code base. There's a lot of companies like these, and they are trapped in survival mode.
> So, the question is, is it unprofessional to abandon ship just 6 months in or given the circumstances is exactly what I should do in order to protect my well being and my career prospects (the project is a slow motion train wreck IMO).
There's really only a few things you can do: If you want to fix the problem, ask to do so. Be prepared with a plan to do so (here's what I'll need, and here's how we'll approach fixing it). Helping a team out of a corner they've been painted into can be very rewarding, but it's an emotional challenge. If the answer is no, or you don't want to fix it, then get another job and leave. There is nothing wrong with that.
This sounds like a company that is frozen by it's legacy code base. There's a lot of companies like these, and they are trapped in survival mode.
> So, the question is, is it unprofessional to abandon ship just 6 months in or given the circumstances is exactly what I should do in order to protect my well being and my career prospects (the project is a slow motion train wreck IMO).
There's really only a few things you can do: If you want to fix the problem, ask to do so. Be prepared with a plan to do so (here's what I'll need, and here's how we'll approach fixing it). Helping a team out of a corner they've been painted into can be very rewarding, but it's an emotional challenge. If the answer is no, or you don't want to fix it, then get another job and leave. There is nothing wrong with that.