MongoDB Q1 Download Numbers

MongoDB
April 26, 2010
#Releases

The MongoDB team is very excited about how the developer community is building around MongoDB, and we wanted to share some numbers.

These are download numbers for the core server for January through March.  It is exactly the number of downloads of the core database from downloads.mongodb.org minus all bots (all known plus anything with bot in the user-agent) and all other crawlers we determine.  We use these numbers internally, so we do try and keep them accurate.

January    15647
February  23226
March      37144

We are very excited about these numbers – please spread the word and help us continue growth of MongoDB!

-Eliot

← Previous

MongoSF is Sold Out

In three weeks over 200 developers will gather in San Francisco to learn about, discuss, and hack on MongoDB at the first conference dedicated to Mongo. The multi-track conference includes sessions on schema design, administration, sharding, replication, and more, led by the 10gen developers working on the database. Also on the MongoSF agenda are several presentations on real-world deployments of MongoDB. Emmett Shear, the CTO of Justin.tv , will lead a session on event logging. Tony Tam of Wordnik - which is storing 1.2TB of data in over 5 billion records - will discuss moving from MySQL to Mongo. As Ryan Angilly recently blogged , he will talk about the process of getting MongoDB up and running in short order at Punchbowl Software . Michael Bryzek will explain how Gilt Groupe , one of the fastest-growing startups in the country, is using Mongo for real-time analytics. John Nunemaker and Steve Smith of Ordered List and RailsTips fame plan to showcase their OM MongoMapper and their Mongo-powered CMS Harmony App . 10gen is excited to be co-sponsoring MongoSF with Hashrocket and Dreamhost. Hashrocket developed Mongoid and recently completed a million-dollar project in which they built a pharmaceutical application with Mongo. Dreamhost provides Linux-based web hosting and offers instant configuration and deployment of MongoDB. If you didn’t register in time, there is still opportunity to attend. We’re looking for 4 volunteers to help with the event. Also, please add yourself to the waitlist - we’ll provide information on recordings, slides, and other resources from the event. MongoSF Volunteers Responsibilities Arrive early to conference for short orientation Assist with setup and registration Monitor one “track” of the conference Keep time and give speakers warnings (e.g. 5 minutes, wrap up, etc.) Set up and manage A/V and recording (bonus if you can lend us a camera for the day!) Direct attendees to the appropriate rooms and answer questions Benefits Access to sold out conference and after-party MongoDB polo shirt Invitation to dinner with the speakers and 10gen team the night before the conference To apply Email meghan@10gen.com one paragraph about why you’d like to volunteer!

April 9, 2010
Next →

MACH Aligned for Retail (Microservices, API-First, Cloud Native SaaS, Headless)

Across the Retail industry, MACH principles and the Mach Alliance are becoming increasingly common. What is MACH and why is it being embraced for Retail? The MACH Alliance is a non-profit organization fostering the adoption of composable architecture principles. It stands for Microservices, API-First, Cloud-Native SaaS and Headless. The MACH Alliance’s Manifesto is to: “Future proof enterprise technology and propel current and future digital experiences" The MACH Alliance and the creation of this set of principles originated in the Retail Industry. Several of the 5 co-founders of the MACH Alliance are technology companies building for retail use cases: for example commercetools is a composable commerce platform for retail (built completely on MongoDB). MongoDB has been a member of the MACH Alliance since 2020, as an “enabler” member, meaning use of our technology can enable the implementation of the MACH principles in application architectures. This is because a data layer built on MongoDB is ideal as the basis for a MACH architecture. Members of our Industry Solutions team sit on the MACH technology, growth and marketing councils, and actively are involved with furthering the adoption of MACH across the Retail Industry What is MACH, why is it important for retail? The retail industry has long been a fast adopter of technology and a forerunner in technology trends. This is because of the competitive nature of the business leading a drive towards innovation- its vital that retails are able to react quickly to new technologies (e.g. NFTs, VR, AI) to capture market share and stay ahead of the competitors. Retailers have realized that to be able to deliver new and value-add experiences to their customers, they have to cut back on operational overhead that leads to increased cost and build standard functionality that can either be bought or re-used. This is where the benefits of MACH comes in- it's all about increasing the ability to deliver innovation quickly while lowering operational costs & risk. Microservices: An approach to building applications in which business functions are broken down into smaller, self-contained components called services. These services function autonomously and are usually developed and deployed independently. This means the failure or outage of one microservice will not affect another and teams can develop in parallel, increasing efficiency. API-First: A style of development where the sharing and use of the data via API (application programming interface) is considered first and foremost in the development process. This means that services are designed to aid the easy sharing of information across the organization and simple interconnectivity of systems. Cloud-Native SaaS: Cloud-native SaaS solutions are vendor-managed applications developed in and for the cloud, and leveraging all the capabilities the cloud has to offer, such as fully managed hosting, built-in security, auto-scaling, cross-regional deployment and automatic updates. These are a good fit for a MACH architecture as adopting them can reduce operational costs and frees up developers for value-add work like new unique customer experiences. Headless: Decoupling the front end from the back-end so that front ends (or “heads”) can be created or iterated on with no dependencies on the back end. The fact that the layers are loosely coupled decreases time to market for new front ends, and encourages the re-use back-end services for multiple purposes. It also de-risks change in the long term as services can function independently. Where does MongoDB come in? MongoDB is an enabler for MACH, meaning that using MongoDB as your data layer helps retailers and retail software companies. achieve MACH compliance. Our data model, architecture and functionality empower IT organizations to build in line with these architecture principles. During a digital transformation, where a retailer is modernizing a monolith into a microservices based architecture, they're looking for a data layer which will enable speed of development & change. MongoDB is the "most wanted" database 4 years running on Stack Overflow's developer survey- this is because our document model maps to the way developers are thinking & coding, and the flexibility allows for iterative change of the data layer. When looking at API based communication, the standard format for APIs is JSON, which again maps to MongoDB's document model. The idea with API-first development is to develop with the API in mind- why not store the data the way you're going to serve it by API. This reduces complexity and increases performance. Cloud Native and SaaS products have become the norm as retailers wish to reduce maintenance and management work. MongoDB Atlas, provides a database-as-a-service, guaranteeing 99.995% uptime, automatic failover and self-healing and allowing DevOps engineers to spin up databases in minutes or by API/ script. Many retail software companies are also built on MongoDB Atlas- for example commercetools, which provides an ecommerce solution as a SaaS product. Headless architectures require a data layer that is able to adapt and change for new workloads. The ability to change the schema at runtime, with no downtime, makes MongoDB's document model ideal for this. Performance and the ability to scale for new "heads" is also important. MongoDB is known as a high performance database and can scale vertically automatically or scale out horizontally seamlessly. So MongoDB becomes a great choice for retailers choosing to adopt a MACH architecture (see figure 1 below). As a general purpose database with high performance, a rich expressive query language and secondary indexing, MongoDB is a really good fit as a data layer as it is capable of handling operational and analytical needs of the application. FIgure 1: Example of a MACH architecture Want to know more? Are you interested in a transition to MACH? Dive into our four part blog series exploring each topic in detail and how MongoDB supports each of these principles: Microservices API-First Cloud-Native SaaS Headless

February 1, 2023