MongoDB Laravel Integration Now Officially Supported

Rishabh Bisht
November 6, 2023 | Updated: February 1, 2024

We are excited to share that MongoDB has taken over development of the community-driven MongoDB integration for Laravel framework, making it a first-class citizen in our product portfolio.

Formerly known as jenssegers/laravel-mongodb, the library delivers a seamless experience for the PHP developers using MongoDB by extending Eloquent, Laravel’s built-in ORM, adding functionalities like Eloquent models, query builder, and transactions. As many in the Laravel community must be aware, the library was in need of a higher degree of support and investment; users have been requesting ongoing maintenance and updates, and we've heard you loud and clear. We understand the importance of an official, robust, and well-maintained library that integrates seamlessly with Laravel. With MongoDB taking over the library, you can expect regular updates with improvements to the functionality, bug fixes, and compatibility with most recent Laravel and MongoDB releases.

We are strongly committed to our PHP Laravel community, providing you with the tools to have a modern and elegant developer experience with MongoDB. Thanks to everyone who contributed to the development of the library as we highly value community contribution and engagement.

To use MongoDB with Laravel framework, check out the latest release of this library, which added support for Laravel 10 - Laravel MongoDB 4.0.0. If you’re just getting started with MongoDB PHP projects, we have a tutorial on how to build a Laravel + MongoDB back end service and documentation for the library. Give it a try today and let us know what you think! Please report any ideas, bugs, or feedback in the PHPORM JIRA project.

← Previous

Darwinbox Scales Up and Out with MongoDB

Tech startup Darwinbox has seen exponential growth since its first line of code was written in 2015. Today, the HR Software-as-a-Service (SaaS) platform handles all employee interactions from recruitment to retirement, is present in 116 countries, and has over 850 customers and more than 2.2 million daily users. What’s more, Darwinbox has been recognized as the number one human capital management (HCM) solution by Gartner and secured investor backing from such big-name players as Sequoia, TCB, Salesforce, and Lightspeed. "The journey," says Shailendra Gupta, Director of Engineering at Darwinbox – with zero understatement – "has been fantastic." Shailendra and colleague, Brahma Prakash Chary Deegutla, Senior Director – Engineering, Product Development at Darwinbox presented at MongoDB.local Delhi where they shared more of that "fantastic journey" and how MongoDB fits into it. On top of Darwinbox sits a robust framework that gives HR leaders a holistic view of employees and the organization. An AI-powered chatbot provides a single interface whereby employees can interact with the system. If someone wants to request leave, access travel policy documents, or submit expenses–whatever the HR representative needs –the chatbot can help meet it, 24/7. With 2.2 million plus employees accessing the portal the volume of data generated is massive; over 250TB of data is in the system. While the pace at which Darwinbox is growing into different geographies leads to an even greater increase in data volumes and users, prompting this ambitious tech company to ask; "How do we address the data locality, and how do we address scaling?" "The answer," says Brahma, "is MongoDB." Given the multidimensional nature of the data and the scale at which it’s growing, Darwinbox needed, "A flexible schema, good scalability, robust security, and documents-based storage–and all this comes as a package with MongoDB Atlas ." "MongoDB, a document-search, document-based database, with capabilities for the aggregation framework, delivers amazing performance and it’s helping us provide near real-time insights to HR leaders." Before MongoDB Atlas, provisioning and managing the instances had to be done by the Darwinbox team; setting up configurations, upgrades, monitoring, backups, and restorations were all done internally – consuming considerable time and human resources. "With MongoDB Atlas, all these problems are solved" says Shailendra, "The architecture is lean, the search facility is quick, the managed service is amazing." And the flexibility afforded by MongoDB brings added value to a fast-growing and changing company. "MongoDB makes it very easy to adapt for any new changes or customizations," says Brahma. "MongoDB has become an integral part of our infrastructure," he adds, "enabling us for our growth expansion and business operations."

November 6, 2023
Next →

Staff Engineering at MongoDB: Your Path to Making Broad Impact

Andrew Whitaker is a Senior Staff Engineer at MongoDB. His previous experience spans tiny startups to enormous organizations like AWS, where he held several different roles focusing on databases. Before joining MongoDB, he worked at a startup building optimized machine learning models in the cloud. Read on to learn more about why Andrew decided to join MongoDB in a senior-level engineering role and how his work is driving improvement within our engineering organization. Why MongoDB I have long been a fan of MongoDB’s products and services. MongoDB the database has always been a pleasure to work with – the system “brings joy” to quote a phrase. As a Python developer, I appreciate how the Python driver feels “Pythonic” in a completely natural way. The programmer interacts with the database using Python constructs: dictionaries, lists, and primitive types. By contrast, SQL databases force me to change my mental model, and the query language feels like an add-on that does not blend with the core language. As an engineer, I am always looking to expand my knowledge and grow my skills. The scope of challenges engineers face at MongoDB is what triggered my interest in the company. We obviously have people working on core databases and distributed systems. But, we also have teams dedicated to machine learning, streaming data, analytics, networking, developer tooling, drivers, and many more areas. It is very hard to get bored working at MongoDB. Finally, I would be remiss if I did not mention the people. Overall, MongoDB’s engineering culture prioritizes intelligence, low ego, and an ability to get stuff done. CL/CI (Continuous Learning, Continuous Improvement) Working at MongoDB has provided me with opportunities for continued learning and growth. Though I do not program as much as I did earlier in my career, I have recently been exploring the Rust language. I’m excited by Rust because it avoids the tradeoffs between predictable performance and safety. My work in the search space has given me exposure to the fast moving world of AI: vector embeddings, RAG, etc. For various reasons, I think MongoDB is uniquely positioned to do well in this area. On top of this, I’m working on some initiatives that are not fully public. I can say that one focus area is improving the sharding experience for our customers. We believe MongoDB sharding is best-in-breed. Still, the process requires more manual configuration than we think is ideal: customers select the shard key, cluster type, shard count, etc. We give guidance here, but I think we can raise the bar in terms of offering a seamless experience with less “futz”. I’m also working with the search team. We believe there is a natural affinity between MongoDB’s document model and AI/ML workloads. We have some features in the works that extend this integration in new and interesting ways. I also spend a fair bit of time driving quality improvements across our suite of products. Our CTO Jim Scharf frequently refers to our “ big 4 ” goals: security, durability, availability, and performance. These goals are more important than any feature we build. I’ve been working across the company to help teams define their availability SLO/SLAs. It turns out that measuring availability is a subtle topic. For example, a naive approach of counting the percentage of failed requests can underestimate downtime because customers make fewer requests when a service is unavailable. So, the first step is to clarify the definition of availability. Finally, as a lapsed academic (in a distant life, I was a graduate student at the University of Washington Department of Computer Science and Engineering), I’m always interested in finding ways to bridge theory and practice. I’ve been collaborating with some folks in our research team to drive improvements to our replication protocols. There are theoretical results that suggest it is impossible to simultaneously achieve low latency and strong consistency (“linearizability” in the technical jargon). However, we believe there are intermediate points in the consistency/latency spectrum that have not been fully explored. This work hasn't been made into a product yet, but stay tuned. Flexible working MongoDB is a hybrid company. Like many of our engineers, I work outside the company headquarters in New York City (I live in Seattle). I appreciate MongoDB’s approach to hybrid working and that company leadership, starting with Dev , cares about the well-being of their employees. It seems there are companies that don’t seem to trust their employees to make decisions, such as which days to come into the office, so I’m thankful for the autonomy I receive at MongoDB to work in a way that’s best for me. Remote work has its challenges, but I would say that the benefit for my work/life balance has been transformative. Final thoughts I have found MongoDB engineers demonstrate a strong mix of technical depth, pragmatism, and empathy. I have yet to find the “smart jerk” prototype that seems to exist throughout the tech industry. Overall, I have found MongoDB is open to change and growth at both the team level and the individual level. There is a willingness to evolve and improve that aligns with the company’s values and leadership principles and enables the success of our technology and people. Find out more about MongoDB culture and career opportunities by joining our talent community .

November 20, 2024