4 ms·
I have the pleasure of working with massive health systems who don't want to upgrade their system to use new API specifications from their vendors. Over the la
by bearjaws 8y ago
I have the pleasure of working with massive health systems who don't want to upgrade their system to use new API specifications from their vendors.
Over the last 10 years we have made 5 new versions of our API, and most of our customers are all using the oldest version.
Maintaining those old servers/endpoints is starting to add up, so we are in the process of migrating all our v1 and v2 APIs to use our latest API using Node Red.
Node Red has every piece of functionality we need to present the same exact API that our customers are currently using, but backed by our most (easily) maintained version.
There are some corner cases where the new API doesn't quite match the old API, but we can still reuse the old API routes as needed, or migrate that functionality into a newer one if desired.
So far we have been able to transparently migrate customers away from their existing version without a hitch.