We’re doing a webinar on MongoDB on Oct 30, 2009 noon EST. It’ll be an overview of MongoDB & will also have Ian White from Business Insider talking about how they are using MongoDB in production:
Details & register at: http://mongodb1.eventbrite.com/
(The webinar is FREE)
We’ve been speaking about MongoDB at physical events like conferences and meetups. But since there’s interest in MongoDB from many different geographical locations, we thought we’d also do a webinar. This will be an interactive live web event. Look forward to seeing you there!
If you have questions on the webinar or have ideas for other such webinars shoot us an email at email@example.com.
Databases Should be Dynamically Typed
Software developers often debate the pros and cons of static versus dynamic typing in programming languages. Yet what about databases? Of course, static typing is traditional for databases. In a relational database we usual declare our columns and the datatype of each column’s values. However, we now see in the nosql space what are known as “schemaless” databases. Technically these products are often have some schema: for example in MongoDB we define collections and indexes. However, we do not predefine the structure of objects within those collections – they may all be different, or all the same. The typing is dynamic. Dynamically typed databases are a good fit with dynamically typed programming languages. It certainly feels like it would be a win to have a dynamically typed db when using a dynamically typed programming language (Ruby, PHP, Python, Erlang, …) How suboptimal it would be to have all the flexibility of dynamic typing in our code, and then hit a “brick wall” when we go to persist the data and have to statically spec everything out! There is synergy to be had between the dynamically typed programming language and the dynamically typed database. Dynamically typed databases can be a good thing when using statically typed programming languages. The best thing about static typing with compilers is that errors are reported at compile/development time. This is a big win for statically typed languages such as Java and C++. However, even with a statically typed database, type matching errors storing data are only reported at runtime! (That is, our java compiler doesn’t check our MySQL schema.) Thus some of the power of static typing in programming is lost at the storage layer. We still retain some benefits: assurance of some consistency to the data stored. But any failure to honor such a contract is only reported at runtime. Thus, it is more than worth considering using a “schemaless” database with say, Java, and getting out of the business of writing data migration scripts with each release. (Yes, some of that work stays but we can eliminate the majority.) Relational databases could be dynamically typed. While existing RDBMSes are statically typed, this is not an inherent limitation of the relational model. One could imagine a relational database with tables where one can dynamically insert a row with an extra column value at any time, and where values of cells in the same column of a table may have different types.
MongoDB and IONOS: Helping European Organizations in Regulated Industries Move to the Cloud
As MongoDB continues to grow as a company, we remain focused on understanding our customers’ unique needs based on their industry and region, among other factors. With this in mind, we are excited to partner with German cloud provider IONOS to help European organizations in regulated industries harness the power of their data to build first-rate applications that also align with security, compliance, and sovereignty requirements. "We want to offer our customers the opportunity to use best-in-class solutions,” said IONOS chief customer officer Martin Endreß about MongoDB becoming part of IONOS’s database-as-a-service offering. “With MongoDB, we are now integrating with the global leader in the NoSQL segment,” he said. “In addition, our companies share fundamental values such as a commitment to full data portability and a rejection of vendor lock-in." With more than 90K servers across 16 data centers, IONOS has a strong footprint in the public sector and other industries where cloud usage is constrained by compliance or data sovereignty needs. Now IONOS customers can drive application innovation in the cloud using MongoDB’s developer data platform while keeping control of their data, aligning with the strongest initiatives in digital sovereignty. The popularity and promise of cloud computing has led an ever-increasing number of businesses to shift their infrastructures and software, including databases, to managed services, and highly regulated industries are no different. Compliance, security, and innovation need not be at odds with each other. Working together, MongoDB and IONOS provide developers with a platform that lets them build, deploy, and run applications securely. MongoDB and IONOS are working closely to develop this new partnership — which is expected to be on offer in fall 2022 — and support customers during implementation. Both Enterprise Advanced and Community versions of MongoDB will be available with IONOS. Learn more about finding a MongoDB partner or becoming one.