Amazon DocumentDB (with MongoDB compatibility) is a fast, scalable, highly available, and fully managed document database service that supports MongoDB workloads. In this tech talk, we will introduce Amazon DocumentDB and its unique architecture that makes it easy to run, manage & scale MongoDB-workloads in the cloud. Amazon DocumentDB is designed from the ground-up and uses a unique, distributed, fault-tolerant, self-healing storage system that automatically scales storage. Additionally, with Amazon DocumentDB's architecture, the storage and compute are decoupled, allowing each to scale independently. Through common use cases, we'll discuss why this architecture helps developers reach faster to their business needs. We'll also talk about how developers can use the same MongoDB application code, drivers, and tools as they do today to run, manage, and scale workloads on Amazon DocumentDB without having to worry about managing the underlying infrastructure.
The changes that MongoDB are bringing to the world in 4.0 are tempting to many companies and administrators, but if you are on an older version such as 3.2, upgrading with minimum disruption can be challenging.
Some of the problems that a company might face are that older language drivers versions may not be compatible with newer versions of mongo, the upgrade path might change, and there is a lot of documentation to read before you embark on the upgrade path.
If in 3.2 the config servers could be both mirrored or replica sets, in 3.4, it's a must to have the config servers as replica sets. Upgrading without interruption can be difficult. With so many things to read about, it's always good to have a reference that will give you an understanding of things that you should consider. A form of cheat sheet.
In this 50 minutes session, I would like to present the steps needed to move from 3.2 to 3.4, which will include some tips to upgrade the config servers to replica sets with minimal disruption and from 3.4 to 3.6 and from 3.6 to 4.0, again, with minimal disruption.
The session will also mention best practices that will apply when running any version upgrade.
Either because of a new feature, a bug, or just for archival purposes, it is often necessary to update or remove large amounts of documents in production.
The challenge with this type of operation is not only to design an efficient process query-wise, but to be able to execute it in production without debilitating the servers or causing secondaries to lag.
There are strategies that can be used to create highly controlled write processes that could run for days under the radar, getting the job done without greatly impacting your application's performance.
In this session, I'm going to share with you key points to consider when creating massive write operations in MongoDB, examples of real-life processes executed, and a few lessons learned.
Redundancy and high availability are the basis for all production deployments. With MongoDB this can be achieved by deploying a replica set. In this talk we'll explore how MongoDB replication works and what are the components of a replica set. Using examples of wrong deployment configurations, we will highlight how to properly run replica sets in production, whether it comes to on-premise deployment or in the cloud.
- How MongoDB replication works
- Replica sets components/deployment typologies
- Practices for wrong deployment configuration
- Hidden nodes, Arbiter nodes, Priority 0 nodes
- Availability zones and HA in single region
- Monitoring replica sets status
In this presentation, we will discuss how to create custom rules when the default rules are not enough for the application.
Have you needed to give a more permissive rule to a user just because of this user wanted to run a specific command?
Also, we will discuss how to use view for hiding fields from users when we don't want them to read all the collection. If you have concerns about security come to this talk.
FoundationDB is a distributed database designed to handle large volumes of structured data across clusters of commodity servers. It organizes data as an ordered key-value store and employs ACID transactions for all operations. Document Layer is a stateless micro server on top of FoundationDB that allows management of JSON documents at large scale. It exposes the traits of FoundationDB through document data model, such as fully ordered documents, consistent indexes, and serializable transactions. It does all this while maintaining wire compatibility with MongoDBÂ® API. As the compatibility is done at wire level, existing MongoDBÂ® tools and drivers work seem less. In this talk, we explore how FoundationDB core strengths play well together with the document data model to make it an easier to use and reliable database.
MySQL JSON Support
Open source reject license
MySQL Group Replication
Distros dropping MongoDB package
This year has seen a good deal of changes and challenges in the MongoDB Space. But where are things going? We are going to cover the most common questions I get asked even today.
What are my risks if I keep using it?
Is MySQL/Postgres Proxy, replication, and HA finally catching up?
Why is JSON support not the only thing to consider?
Will MongoDB lose my data?
Past these I will be discussing the ecosystem as a whole, and how I see the next few years shaping out. While this talk is most helpful for business leaders and architects, for DBAs and engineers it will also help you decide what to focus on in your career for the emerging technology future.
In a sharded MongoDB cluster, scale and data distribution are defined by your shard keys. Even when choosing the correct shards key, ongoing maintenance and review can still be required to maintain optimal performance.
This presentation will review shard key selection and how the distribution of chunks can create scenarios where you may need to manually move, split, or merge chunks in your sharded cluster. Scenarios requiring these actions can exist with both optimal and sub-optimal shard keys. Example use cases will provide tips on selection of shard key, detecting an issue, reasons why you may encounter these scenarios, and specific steps you can take to rectify the issue.
In this day and age, maintaining privacy throughout our electronic communications is absolutely necessary. Creating user accounts, and not exposing your MongoDB environment to the wider internet, are basic concepts that have been missed in the past. Once that has been addressed, individuals and organizations interested in becoming PCI compliant must turn to securing their data through encryption. With MongoDB, we have two options for encryption: at rest (only available as an enterprise feature with MongoDB) and transport encryption.
In this session we will review
- MongoDB default security
- Additional layers of security
- Audit and Log reduction
- Encryption and why it's important
- Step by step for encryption at rest and in transit
- Percona for MongoDB security features
Learn how to monitor MongoDB using Percona Monitoring and Management (PMM) so that you can:
* gain greater visibility of performance and bottlenecks MongoDB
* Consolidate your MongoDB servers into the same monitoring platform you already use for MySQL and PostgreSQL
* Respond more quickly and efficiently in Severity 1 issues
We'll show how using PMM's native support for MongoDB so that you can have MongoDB integrated in only minutes!
In MongoDB 4.0 the MongoDB community got its first chance to use transactions. Well, except for the short lived TokuMX clone. In this talk I will discuss the capabilities and limitations of the new feature including:
â€¢ Potential impact on concurrency
This is a feature I have long waited for and I can only view as a good thing, extending the uses of MongoDB into realms previously not possible. At the same time, as with any database transactional feature, one has to be careful not to allow the feature to seriously impact concurrency.
Doug will discuss the basic knowledge needed to understand the complications of running MongoDB inside of a containerized environment and then to go over the specifics of how Percona solved these challenges in the PSMDB Operator. It also will provide an overview of PSMDB Operator features, and a sneak peek at future plans.
Introduction, installation, configuration, usage examples.
How to backup and restore to a local file system.
How to backup and restore to an S3 instance.