search

mongodb / stitch-js-sdk

MongoDB Stitch JavaScript SDK
Apache License 2.0
113 stars 67 forks source link

Does MongoDB Stitch have any future in the short and long term? #394

Open andredev24 opened 4 years ago

andredev24 commented 4 years ago

We want to move an e-commerce application that we currently have with Firebase Auth + Firestore, to a BaaS solution like MongoDB Stitch but I am concerned that there is no more support and utilities in the SDK, also the documentation for the Stitch CLI is very poor and incomplete and they should add Typescript to the (CLI) as well. Don't get me wrong I love MongoDB Atlas and the Baas solution they are trying to offer with MongoDB Stitch, but I feel it is lacking more community support and better documentation. I find hundreds of messages on Reddit for example from people trying to switch from other services to MongoDB Stitch but without answers. I understand that the team is working on MongoDB Realm and that they are going to unify the two services into one, my question is whether it is worth moving to MongoDB Stitch and finding the support and support that we as a company are looking for. By the way, you have in mind to integrate the Google Cloud as a third-party service similar to AWS that you already have incorporated, thank you very much for your time.

drewdipalma commented 4 years ago

Hi Andre – Thanks for the outreach. Stitch is very much being invested in for the near term as well as for the future. We've released some major features recently including a GraphQL Service and Dependency Resolution for Stitch Functions (of most requested feature by the community). You should actually be able to use dependency resolution to integrate with different GCP services today. The CLI is definitely an area where we want to work more closely over the next few months, so stay tuned there and feel free to drop suggestions in our feedback forum.

We're also working hard on our roadmap to integrate Realm and Stitch together. We will rename Stitch to MongoDB Realm in near future, but we won't be changing anything about Stitch works, just re-branding and adding new features.

We do our best to respond to issues on Github as well as the MongoDB Community Forums but it sounds like we could also do a better job monitoring Reddit. We're ramping up the team and we'll try to address this better in the future. Is there anywhere specifically we should be looking for posts?

ivanjeremic commented 4 years ago

Hi Andre – Thanks for the outreach. Stitch is very much being invested in for the near term as well as for the future. We've released some major features recently including a GraphQL Service and Dependency Resolution for Stitch Functions (of most requested feature by the community). You should actually be able to use dependency resolution to integrate with different GCP services today. The CLI is definitely an area where we want to work more closely over the next few months, so stay tuned there and feel free to drop suggestions in our feedback forum.

We're also working hard on our roadmap to integrate Realm and Stitch together. We will rename Stitch to MongoDB Realm in near future, but we won't be changing anything about Stitch works, just re-branding and adding new features.

We do our best to respond to issues on Github as well as the MongoDB Community Forums but it sounds like we could also do a better job monitoring Reddit. We're ramping up the team and we'll try to address this better in the future. Is there anywhere specifically we should be looking for posts?

So what will happen to all the Stitch apps we have, will they break? & Does it mean Stitch can only be connected to Realm database then and not to a MongoDB Cluster?

Far as I understand this Realm is a database running on devices and MongoDB atlas is in the cloud so the new rebranded Stitch will be able to work with MongoDB & RealmDB same time together correct? Can we then use our MongoDB Cluster only or do we need to use both?

drewdipalma commented 4 years ago

Hi Ivan – Your Stitch app will not break as we re-brand/merge the products. All endpoints, SDKs, and Triggers will continue to process requests as they do today.

We will be releasing a MongoDB Realm SDK across all platforms which will have the same features that the existing Stitch SDK has (and will replace the Stitch SDKs in the long term). For the iOS and Android SDKs, this SDK will have the option to use the Realm Database and enable syncing directly from it to MongoDB Atlas. Any new features we introduce will be optional.

ivanjeremic commented 4 years ago

Hi Ivan – Your Stitch app will not break as we re-brand/merge the products. All endpoints, SDKs, and Triggers will continue to process requests as they do today.

We will be releasing a MongoDB Realm SDK across all platforms which will have the same features that the existing Stitch SDK has (and will replace the Stitch SDKs in the long term). For the iOS and Android SDKs, this SDK will have the option to use the Realm Database and enable syncing directly from it to MongoDB Atlas. Any new features we introduce will be optional.

Thanks, nice to hear this! Wouldn't it be better to have all features available via API so we don't need an SDK? For example for Login, Register, etc.. API REST Endpoints and if GraphQL Enabled Mutations for Login Register, etc.. So all we need in our apps is to interact with an API.

There is this project called Strapi it is not a BaaS but it could be if they would host it for clients somewhere, the REST/GraphQL API you get there does exactly this and it is very nice to work with, maybe this is something Stitch team can look into it, with this it would be truly a BaaS.

drewdipalma commented 4 years ago

Hi Ivan – While we think the SDKs provide a better experience, you do always have the option of hitting the Client APIs directly.