Here too, each database has a different approach that needs to be learned.

Stats and metrics - to oversimplify, document databases give you more freedom than relational databases. But the cost of freedom is that you’re more likely to run into gotchas. It’s especially important that the GUI provide event logs and performance stats for debugging and identifying bottlenecks.Ĭlustering - one rationale for the creation of the first “NoSQL” databases was the need for horizontal scalability, so we might expect the GUI to help visualize and manage a distributed database. MongoDB Tutorials and Articles: The Complete Collection. Obviously, this all depends on your specific needs. When you have many concurrent users, you'll want to use clustering to achieve high availability if you need to improve the speed of heavy queries, you'll want tools that help you resolve bottlenecks, and so on. Let’s get started, going from most basic to most advanced. CouchDB's FauxtonĬouchDB is a mature database with plenty of features, but its GUI Fauxton (formerly named Futon) is pretty minimal. Couch’s primary interface is an HTTP API, typically used through cURL. Fauxton is built on top of this API with each page representing an equivalent endpoint.

It runs as part of the server itself and is accessible by browser at /_utils. In all the databases we’re looking at, documents are written and stored as JSON. For each database, Fauxton lets you view documents either in their native JSON or as a table. In the table view, you can select 'show all columns', meaning there's one column for every field found in any of the documents. Frustratingly, there’s no scrolling left and right, so the columns just get squished together: Sometimes your documents all happen to have the same structure, but if there’s even a little variety, this gets impractical fast.

Mac mongo gui