-
-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chapter 2: mLab is becoming a part of MongoDB Atlas #138
Comments
Do you know something is wrong with Atlas? |
@YuriGor Haven't researched Atlas but prefer smaller, private companies. Something like Zeit for hosting apps. |
@YuriGor Here are a few thoughts. I just deployed this app https://github.com/async-labs/saas on MongoDB Atlas, AWS, M10 cluster, us-west-1. I did not do benchmarking but for the same app, DB region, my location, and internet speed - server-side rendered pages load a bit faster with the above MongoDB Atlas cluster ($65/month) compared to dedicated mLab cluster ($180/month). UX/UI/simplicity/intuition is worse at MongoDB Atlas compared to mLab, I guess that they are more focused on Enterprise level customers. Since their stock soared recently, I bet they will keep buying competitors and making open source code harder to use for small companies. |
Did you see scalegrid.io? |
@YuriGor Much friendlier UX/UI and performance is good. At the Scalegrid's dashboard:
Can you confirm? |
Can't confirm, sorry, I didn't try it, since I have no my own cloud environment. |
I also found nice mongo UI Using dbaas's ui for admin tasks is ok, but for development purposes it's more comfortable to use something locally. This is screenshots how I connected to my mLab test collection: As expected, works much faster than mLab's ui. |
Note to self, we should update the book's content in Q1 2019 when mLab shuts down. So far I am happy about MongoDB Atlas. |
@klyburke @YuriGor @delgermurun I replaced |
Think you also can update the readme where this issue is referenced now then ;) |
@kvsm Good point, done. |
The text was updated successfully, but these errors were encountered: