Update September 18, 2017: Everyone has now been transferred to the new databases, and everything appears to be working without a hitch. There is one remaining step, transferring the non-document data (emails, settings, etc), which will happen on Wednesday, Sept 20th at 9:14pm Pacific Time, and will require a few minutes of scheduled downtime (we are expecting 20 minutes of downtime, but it could take as long as an hour). You should still be able to use WorkFlowy in offline mode during the downtime.
Update September 11, 2017: We have now begun the process of transferring everyone to the new databases. At this point, around 300 existing users have transferred to the new databases, and we’ve also been putting new users on the new databases. In sum, that’s around 4,000 people on the new databases with no reports of data issues.
WorkFlowy is close to outgrowing the largest single database on offer by Amazon Web Services, where we host the application. To deal with this we’ve been engaged in a pretty involved project to split all the data we store across many different databases.
Internally we’ve been using the new database cluster for about a week, and we’ll soon start transitioning everyone over. Before we do that, however, we want a few intrepid souls to try the new database setup and report if they’re having any unexpected behaviors when using WorkFlowy. We haven’t had any issues with the new setup yet, so hopefully you won’t either, but we’d still appreciate your help kicking the tires.
Here’s a link where you beta test the new database cluster:
Please email any issues you find to email@example.com, thanks for your help!