I obviously won’t ever charge an open source project, since they are honoring the unwritten contract: If I give, you give.

But the days of quick-flip corporations and ingrate programmers making money on my software are over. My new motto is:

Open source to open source, corporation to corporation.

MongoDB is a high-performance, open source, schema-free document-oriented database. MongoDB is written in C++ and offers the following features:

* Collection oriented storage - easy storage of object-style data

* Dynamic queries

* Full index support, including on inner objects

* Query profiling

* Replication and fail-over support

* Efficient storage of binary data including large objects (e.g. videos)

* Auto-sharding for cloud-level scalability (Q209)

Of course the answer is “it depends”, but that’s not very helpful. Let me ask you a few questions to help you figure out which technology is appropriate to your particular application. Then I can give a few pointers so that you can find out more.

The movement's chief champions are Web and Java developers, many of whom learned to get by at their cash-strapped startups without Oracle by building their own data storage solutions, emulating those being built by Google Inc. and Amazon.com Inc., and which they subsequently released as open source.

Now that their open source data stores manage hundreds of terabytes or even petabytes of data for thriving Web 2.0 and cloud computing vendors, switching back is neither technically, economically or even ideologically feasible.

Like the Patriots, who rebelled against Britain's heavy taxes, NoSQLers came to share how they had overthrown the tyranny of slow, expensive relational databases in favor of more efficient and cheaper ways of managing data.

Current handcrafted approaches to compiler development are no longer sustainable. With each generation of re-configurable architecture, the compiler development time increases and the performance improvement achieved decreases. As high performance embedded systems move from application specific ASICs to programmable heterogeneous processors, this problem is becoming critical.

This project explores an emerging alternative approach where we use machine-learning techniques, developed in the artificial intelligence arena, to learn how to generate compilers automatically.

Object identity is deceptively hard to implement correctly when objects are persisted to a database. However, the problems stem entirely from allowing objects to exist without an id before they are saved. We can solve these problems by taking the responsibility of assigning object IDs away from object-relational mapping frameworks such as Hibernate. Instead, object IDs can be assigned as soon as the object is instantiated. This makes object identity simple and error-free, and reduces the amount of code needed in the domain model.

mod_auth_tkt is a lightweight single-sign-on authentication module for apache, supporting versions 1.3.x, 2.0.x, and 2.2.x. It uses secure cookie-based tickets to implement a single-signon framework that works across multiple apache instances and servers.

mod_auth_tkt itself is completely repository-agnostic, as the actual authentication is done by a user-supplied CGI or script in your language of choice (examples are provided in Perl, with contrib libraries for use with python and PHP). This allows authentication against virtually any kind of user repository you can imagine (password files, ldap directories, databases, etc.)

This is a step-by-step tutorial guide for implementing OpenID consumer-side support with a web site that already has users with accounts. It will explain how to easily let new users sign up for an account on your site using their OpenID URL and how to let existing users attach their OpenID(s) so they can sign in using them.

American-style hackers don't just make for bad team members; they also make for bad programmers, albeit for reasons new grads seldom anticipate. "Cowboy coders" might be technically proficient, but their code is less likely to be maintainable in the long term, and they're less likely to conform to organizational development processes and coding standards. As a result, quality assurance -- including testing, debugging, code reviews, and refactoring -- are likely to suffer.