Once you replicate the data, you replicate the APIs and generate the sdks. Got it. But then how much work to change my front end components on the like 30 visualizations I have to actually use them? And to validate them?
If your new APIs use the same endpoint names and the same request/response schema (same field names, types, shape), then swapping the base URL in your fetch calls could get you most of the way there without touching your visualization components.
In practice I get that there’s usually some drift, like maybe a field is renamed or you have different error handling. Depending on how strictly your front-end components assume the old schema, you’ll need to update those areas.
Once you replicate the data, you replicate the APIs and generate the sdks. Got it. But then how much work to change my front end components on the like 30 visualizations I have to actually use them? And to validate them?
If your new APIs use the same endpoint names and the same request/response schema (same field names, types, shape), then swapping the base URL in your fetch calls could get you most of the way there without touching your visualization components.
In practice I get that there’s usually some drift, like maybe a field is renamed or you have different error handling. Depending on how strictly your front-end components assume the old schema, you’ll need to update those areas.
co-pilots tend to be really effective at this kind of migration work. especially once you've got the before and after schemas as types in your code.