This improvement should make use of Robomongo more efficient than its ever been. We think, that in place edit is the one of the best UX improvements we can make. This feature, along with two above, are our first priority and should cover needs of the major part of the Robomongo community. The support of the Replica Sets is one of the most awaiting features. MongoDB 3.2 soon will be a production-ready release and we plan to focus on that release first, while still considering support for all versions of MongoDB. To support all versions of the MongoDB we need to implement V8 JavaScript engine and this is quite a lot of work. But starting from 3.1.9 MongoDB is based on SpiderMonkey again. Since MongoDB 2.3.1, JavaScript engine was changed from SpiderMonkey to Google V8. Support for V8 JavaScript engineĪt the moment, Robomongo is based on the SpiderMonkey JavaScript engine. We plan to add support for WiredTiger first and work on other storage engines, such as In Memory and Encrypted storages right after. From version 3.2 MongoDB starts to use WiredTiger by default. Currently Robomongo only supports MMAPv1 storage engine. Support for MongoDB 3.x storages (WiredTiger and others)įrom version 3.0 MongoDB introduces new pluggable storage architecture and the WiredTiger storage engine. According to Magic Backlog, these features are the most requested by the community. We are planning to address 7 major features in the first 6 months. A rigorous quality assurance alone requires a dedicated person. Now add to all of this cross-platform and native nature of Robomongo, and you will quickly realize how many efforts are needed to deliver this tool to your laptop with Mac/Windows/Linux of version N. Each time you decide to connect to some MongoDB cluster, you will be able to select needed version of pluggable Robomongo Engine. ![]() And such engines should be moved to separate projects. The API between Robomongo GUI and Engine should be defined. That is why one of the important features that should be implemented is a pluggable Robomongo engine: Today we bundle Robomongo with a single version of MongoDB shell and you are lucky if it supports your version of MongoDB. The current model of Robomongo distribution is also requires changes. Should we just support SpiderMonkey, V8 or both? All these mean, that significant efforts are required to support "#1 feature" of Robomongo. Now we cannot be sure, what is a safe bet for JavaScript engine for Robomongo. But in MongoDB 3.2 SpiderMonkey is back again. Starting from the version 2.4, MongoDB began to use Google V8 engine, instead of SpiderMonkey. Even JavaScript engine, used by MongoDB, was changed twice. Integration is not as straightforward as it seems and requires changes of MongoDB source code. Each new version of MongoDB has new version of mongo shell, that should be integrated with Robomongo. The reason why such deep integration with mongo shell is not implemented in other tools - complexity. If you are new to MongoDB shell, Robomongo is the best way to learn it. ![]() If you are familiar with MongoDB shell - then you already know how to work with Robomongo. Today we have many MongoDB administration interfaces, but Robomongo so far is the only tool that is so deeply integrated with MongoDB's mongo shell, that it even embeds it. ![]() If you open Google Trends and compare the most notable MongoDB UIs, you will get this: In order for this to happen, we need your support!ĭespite everything, even today, Robomongo is very popular. With a focus on a single project we could really stir up Robomongo and not only solve most of current major issues, but also implement a number of important new features. One year is a sufficient term to not only solve most of current major issues, but also it will be enough to implement number of new features. My goal is to create a team of C/C++ Developer and QA Engineer who can work on the project at Paralect office without being distracted to anything else for one year. Today, I'm taking my last attempt to rescue the project. Today it is evident to me, that I'm not able to support and develop Robomongo alone anymore. If you watched short movies about Robomongo, you probably know that I'm broken off between Robomongo and my position at Paralect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |