Couchbase Migration GCP to AWS

Hello,

I have very little knowledge about this product. Truthfully i dont even know what it does or how our application uses it. We acquired the application that uses it and no one is around anymore that has knowledge of it. I am working on getting the product moved to AWS from GCP and not really sure where to start.

My first question, is there an AWS Product that does the same thing as Couchbase? Like DynamoDB or DocumentDB?

If there isnt an AWS equivalent then i need to look at migrating the application. We are currently using 6.0.0 so the first thing i need to do is upgrade to 7.2.x which i found the documentation on already that says to go from 6.0 → 6.5 → 7.2x

I was hoping, after the upgrade, to stand up two new servers in AWS and join them to the cluster and failover to them and remove the GCP ones. But i cant find any documentation showing if that works.

I did see there are options to do backups or using XDCR but if i can just failover that seems simpler.

Any advice on finding out what features we use in Couchbase, Upgrading from 6.0.0 to 7.2.x or on Migration from GCP to AWS?

Hi @jreagan, Couchbase being a data platform, it offers a lot of different features. You can start by looking at which services are activated on the Cluster. Data, Query, Index, Fulltext, Analytics, Eventing. Do you know if a Sync Gateway is deployed somewhere as well ? In which case you would be using Couchbase Mobile too.

If they are all active it does not necessarily means that everything is used and unfortunately there is no way to know except looking at the application code.

There is not, too my knowledge, a single AWS product that offers everything Couchbase does. Maybe using several product at the same time? Something for sure is that there are no other products that have a compatible SDK/Protocol, so you would likely have to rewrite your application code.

For the single Cluster/failover option, I would highly discourage it. Because latency between nodes on a cluster distributed over different DataCenters might result in errors. We advise our customers to use XDCR for multi cloud sync.

Thanks for responding Laurent,

From what i can tell its just the Document piece that we use. Under the WebUI it shows Documents, Query, Search, and Indexes but the last 3 features all show text saying something like “You have no xxxxxxxx in this cluster yet.”. We dont have any other services installed for this, This is version 6.0.0 of the Community Edition so i dont think it even has mobile features.

As for the upgrade piece, is there some documentation somewhere showing this whole process? What is the best way to back it up in case of issues during upgrade? For using the document feature, if thats all we use, is there any known issues as far as version differences that could break our application going from 6.0.0 to 7.2.x?

Thanks for your help!

Also, hopefully this question doesnt take this thread out of topic but, our application is all Python based. Are there any SDK issues i need to be aware of going to 6.00 to 7.2.x, Do i need to upgrade it as well? How do i see what version we are using?

Would all of this be easier if i migrated just using 6.0.0 (if its even available) and worried about the upgrade stuff in the future?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.