Man I’ve never seen it not work. It’s pretty much the only pattern I use because it’s so successful. Meanwhile the other teams in my company have numerous failed migrations because they try to rewrite the entire thing at once instead of using the strangler fig pattern.
I suspect that starting your own version of the API is the Software Designer / Software Architect version of Programmers’ “I know best so I’m going to do my part of the code my way which is different from everybody else’s”.
Mind you, at the very least good Software Architects should know best, but sometimes people get the title without having the chops for it.
In my experience, it was an attempt to prune the stuff in old API that wasn’t useful. A successful attempt, since the backend working on it was in the same room as me and I could yell at him.
I don’t get why anyone would publish v2 when it not really on feature-parity. Do companies really start releasing v2 endpoints slowly?
it’s called the strangler pattern, where the new version is layered on top of the old and gradually replaces it.
it usually doesn’t work.
Man I’ve never seen it not work. It’s pretty much the only pattern I use because it’s so successful. Meanwhile the other teams in my company have numerous failed migrations because they try to rewrite the entire thing at once instead of using the strangler fig pattern.
only time i’ve ever tried it was in a duolith consisting of over half a million lines of python, all of them critical.
I suspect that starting your own version of the API is the Software Designer / Software Architect version of Programmers’ “I know best so I’m going to do my part of the code my way which is different from everybody else’s”.
Mind you, at the very least good Software Architects should know best, but sometimes people get the title without having the chops for it.
In my experience, it was an attempt to prune the stuff in old API that wasn’t useful. A successful attempt, since the backend working on it was in the same room as me and I could yell at him.