Well you have to worry about nobody helping you with version 1.00. It’s been end of life since November 2015. There should be very little impact from upgrading it since it doesn’t actually store any data itself (that’s all in Couchbase server). However what is your Couchbase server version then? I hope it is not equally old.
That was was end of life April 2016. The enterprise edition makes things more complicated because there are a few possible scenarios here:
You have just been testing something a lot on AWS, in which case you should definitely upgrade because no one is relying on your service
This is a production deployment and people are consuming this service, in which case you should talk to your support representative that is assigned to your enterprise edition license (who will definitely tell you to upgrade)
This is a production deployment and you haven’t paid for a license, in which case you are violating the terms of service and must switch to the community edition (the latest version) or we cannot continue to talk
I’m hesitating to upgrade. Yes, nobody is relying on my service, but I’m worried I may have to completely rewrite everything I’ve written in the past. I don’t have that kind of time. I want to focus more on the thing I’m testing, not on managing databases.
I don’t know what changed. So it’s the fear of the unknown.
I’m imagining me spending a week trying to get up-to-speed on all the stuff that has changed with sync gateway and the related python API before I can get my web server back up. The web server was written using tornado and depends on the old python API
Python API? You mean this thing? Actually I never heard of it before now. That’s a tough situation but that’s the downside of relying on alpha products (they may suddenly end development like this one seems to have). The REST calls implemented in version 1.0 have not changed in the past years so it should still function the same way especially if you only use simple calls like get and put.