Using MongoDB Atlas for our HR Analytics product, but can't drill down into data. E.g. Attrition analytics -> Go by Location -> drill down into Grade/Band -> Gender, etc.
Atlas is MongoDB's Database as a Service offering. It's not an analytics tool, however, you can leverage your MongoDB databases in Atlas for analytics in one or more of several ways:
https://docs.atlas.mongodb.com/bi-connection/ The BI Connector in Atlas gives you the ability to connect traditional BI Analytics tools like Qlik, Tableau to your MongoDB data directly.
https://docs.mongodb.com/charts/master/launch-charts/ - Charts lets you drill into and create analytical charts directly from the data in your Atlas databases.
Hope this helps.
Related
I want to create and maintain mongodb atlas datalake programmatically but seems there is no option available. I could find out one API which can be used to create/update/delete data lake but that it only allows to set some options. Here is the link I am following - https://docs.mongodb.com/datalake/reference/api/dataLakes-create-one-tenant/#request-body-parameters
Doesn anyone know how to setup other options like data store, storage etc which you can do from mongodb atlas UI?
During my investigation on compatible DBs for IoT data storing I looked into MongoDB and pricing is a little bit confusing.
Just wondering what is the difference between MongoDB Atlas and MongoDB Atlas for AWS as they both work on AWS?
And what is the right way to run MongoDB Atlas on AWS?
As far as I can see, they both should mostly be similar :
MongoDB Atlas :
You can directly go to MongoDB-Atlas portal & create a MongoDB cluster(a cluster will usually be 3-shard/node replica set on which a DB is hosted) on either of the cloud providers (AWS/Google/Azure). This way all database updates/maintenance will usually be done by vendor. Quiet easy & simple - Which most people are opting for these days (SAAS/ db hosted on cloud). You can also opt for a free cluster which should be suitable for basic needs kind of learning MongoDB. While creating cluster you can check for pricing which is based on cluster level (M0 to M700), You can upgrade your cluster when ever you wish to, but when I was creating one I've noted that you would pay upfront for a certain amount of years likely 3 & whether you use the money or not you would not get anything back but it you've paid less then you might be charged over the time of usage. You'll pay bills thru MongoDB Atlas.
MongoDB Atlas for AWS :
From here aws-marketplace when you see the text marketplace (where multiple companies/people collaborate to sell products) it's basically these two companies have collaborated to provide MongoDB as SAAS. With this you can actually come from AWS rather than than Atlas from itself. When it comes to pricing AWS seems to provide some credits, It would be better if you can consult AWS & Atlas to check on their pricing & other terms if you really wanted to use it for enterprise purpose. You might end-up owing an AWS account to pay bills for this usage (Which hectic if you don't use AWS for other use-cases). Additionally if you check below on MongoDB Atlas for AWS page it seems like just a starting point is given at AWS side but entire setup would be done at Atlas.
You're charged for your purchase on your AWS bill. After you purchase
a contract, you're directed to the vendor's site to complete setup and
begin using this software.
I'm very new in the world of "NoSQL", Recently I started using Cosmos DB for JSON documents and am able to store and get data using CosmosDB "SQL" and "Mongo" API.
Which API is best for me? (requirement: Performance, Low Latency, Huge Collection, Low cost)
Now I have spent more than 6 months with Cosmos DB project. I can give my opinion on this question.
Azure Cosmos DB offer the same feature with SQL API vs Mongo API, hence you can't compare by feature.
Reason using Mongo API in Cosmos DB
If you have existing Mongo DB database and you want to migrate on Azure.
If you or your team members have Mongo DB experience.
If you are developing cloud agnostic application, you can move your application on-premise or any other cloud vendor.
Reason using SQL API in Cosmos DB
If you have SQL query experience, it would be easy to start.
If you are not looking cloud agnostic application. (can't move Cosmos DB application on-premise or other clouds vendors).
Cosmos DB Change Feed only available with SQL API.
--- UPDATED 2020 ---
Change Feed is available for all the APIs across all available SDKs except the Table API
Both the API’s provide you high throughput, low latency, elastic scale, geo-replication, etc.
It boils down to what you are comfortable with. Many people preferred Mongo, as they are already familiar with Mongo, it’s syntax, tools, and they already had an application built on Mongo which they migrated to CosmosDB.
If you are starting new, and don’t have an existing investment in Mongo, I will suggest starting with SQL. SQL is the oldest API of CosmosDB, and more battle hardened.
As a software engineer using MongoDB API. I can confirm that my team and I suffered when handling 426 code errors from CosmosDB. So we end up developing our own custom solution with Polly to handles these throttles. Whereas if we used SQL API we would have access to CosmosDB sdk which pretty much handles these situations. This is just my feedback.
Looking to build a react-native app and was going to use MongoDB Atlas for the database, express/apollo/graphql mixed in there for better querying. Has anyone had any experience with these techs together? especialy MongoDB Atlas and express?
I'm not sure how all these techs link together. Any tutorials will be handy as well. Thanks.
MongoDB Atlas provides you the endpoint where you can connect to the replica set and use mongodb.
This takes over many other factors such as installing mongodb, backups and restore. Also, the endpoint(connection string) provided by MongoDB Atlas comes with built-in:
Authentication enabled
Authorized users
Replica set to maintain HA
All of these factors give you advantages of using MongoDB Altas so that you can focus on developing your apps
Using mongodb atlas is likely to give you same things you would expect from your local mongodb and express with additional advantages listed above
If you're planning on using MongoDB and GraphQL in a NodeJs service in the interest of getting better querying capabilities, I'd suggest looking at GraphQL-to-MongoDB, or how I learned to stop worrying and love generated query APIs.
Disclaimer: I wrote that blog post.
MongoDB Atlas just announced GraphQL support for Atlas and Stitch. In a nutshell , you can easily generate/ create Schema for a collection in Atlas, Define access rules, relations and generate queries and mutations. GraphiQL is also integrated to run and test your queries. Check this blog post for more details - https://www.mongodb.com/blog/post/introducing-graphql-support-in-mongodb-atlas-with-stitch
I have MongoDB on Windows and it seems the MongDB BI Connector is not available for Windows.
Will it be made available so I can use e.g. Tableau to analyze my data?
MongoDB team has made MongoDB Compass to visualise data
If you wish to use their payed tool then it's a solution.
(it's free for evaluation and development )
Compass is a great tool, but it's more about data exploration and maintenance than visualisation. While it does show some basic graphs, these are limited to showing the spread of data across a schema.
For a more complete MongoDB data visualisation solution, check out MongoDB Charts. Charts is a first-party MongoDB tool designed to visualise data from your MongoDB collections. You can create charts with a drag and drop interface, arrange the charts onto your dashboards, and embed them into your own applications without code.
Charts is available as a part of MongoDB Atlas, or it can be installed as an on-prem server.