Slashdot Mirror

This is wide-ranging interview with Dev Patel and Poulomi Damany of BitYota, an Analytics as a Service startup that works specifically with MongoDB. Open Source? Not yet. But hopefully soon, they say. And why should an IT person or programmer care about marketing-oriented analytics? Because the more you know about functions in your company besides IT (such as finance, investor relations, and -- yes -- marketing), the more valuable you are as an employee. Dev also mentions the two main things he looks for when recruiting for BitYota: "One is intellect, and the other is attitude." He points out that this is not true merely of BitYota, but of any strong startup. This is all good information for any job-seeker hoping to land a spot with a startup -- and for anyone who is happy with where he or she works but hopes to earn promotions and raises, too.

A mere year since the Mediagoblin photo/video sharing project was started, the project has hit version 0.3.0. Release highlights include: a rewrite of the database from MongoDB to SQL (via SQLAlchemy, making it much easier to install), audio support (using the HTML5 <audio> tag), a first take on a mobile interface, and smarter video buffering. Not content to sit idle, the developers are starting work on Salmon protocol support to federate with software like Diaspora in the next release.

phy_si_kal writes "The new, open source, Opa web programming language just hit version 0.9.0 'S4,' six months after its last major release. Apart from a new syntax more similar to JavaScript, the new release focuses on mongoDB integration. Opa now features something similar to object-relational mapping (ORM) except that mongoDB is a non-relational, document-oriented database and Opa a functional, non-object-oriented language. The new functionality makes the NoSQL database even easier to use, as all language-database calls are automated. The mapping of functional datastructures to documents could even be much better than current ORM approaches and solve the object-relational impedance mismatch."

rick446 writes "I took some time to benchmark the global write lock improvements in MongoDB 2.0. From the article: 'MongoDB, as some of you may know, has a process-wide write lock... Per-database and per-collection locking is on the roadmap ..., but it's not here yet. What was announced in MongoDB version 2.0 was locking-with-yield. I was curious about the performance impact of the write lock and the improvement of lock-with-yield, so I decided to do a little benchmark, MongoDB 1.8 versus MongoDB 2.0.'"

rick446 writes "I took some time to benchmark the global write lock improvements in MongoDB 2.0. From the article: 'MongoDB, as some of you may know, has a process-wide write lock... Per-database and per-collection locking is on the roadmap ..., but it's not here yet. What was announced in MongoDB version 2.0 was locking-with-yield. I was curious about the performance impact of the write lock and the improvement of lock-with-yield, so I decided to do a little benchmark, MongoDB 1.8 versus MongoDB 2.0.'"

rick446 writes "I took some time to benchmark the global write lock improvements in MongoDB 2.0. From the article: 'MongoDB, as some of you may know, has a process-wide write lock... Per-database and per-collection locking is on the roadmap ..., but it's not here yet. What was announced in MongoDB version 2.0 was locking-with-yield. I was curious about the performance impact of the write lock and the improvement of lock-with-yield, so I decided to do a little benchmark, MongoDB 1.8 versus MongoDB 2.0.'"