|
|
|
|
| LEADER |
06095nmm a2200517 u 4500 |
| 001 |
EB001935906 |
| 003 |
EBX01000000000000001098808 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 020 |
|
|
|a 9781484258170
|
| 050 |
|
4 |
|a QA76.9.D3
|
| 100 |
1 |
|
|a Cottrell, Nicholas
|
| 245 |
0 |
0 |
|a MongoDB topology design
|b scalability, security, and compliance on a global scale
|c Nicholas Cottrell
|
| 260 |
|
|
|a [California]
|b Apress
|c 2020
|
| 300 |
|
|
|a 1 online resource
|
| 505 |
0 |
|
|a External authentication -- Encrypted connections -- TLS 1.2 -- Encryption at rest -- Backups -- Auditing, obfuscation of logs -- Proactive security -- Server-side JavaScript -- Input validation and injection attacks -- where operator -- SELinux -- Binary monitoring -- Certification -- Checklist -- Chapter 4: Compliance and GDPR -- General Data Protection Regulation -- Privacy by design -- Caveats -- Data protection -- Key concepts -- Personally identifiable information -- Definitions -- Representatives -- Data portability -- Data size -- Retention of personal data -- Automatic removal
|
| 505 |
0 |
|
|a Balancer -- Shard distribution -- Pre-splitting -- Ascending shard keys and hot shards -- Architecture choices -- Computing resources -- Memory -- Storage -- Bandwidth and latency -- Horizontal scaling -- Round-trip latency -- Private vs. cloud -- Logical databases -- Key takeaways -- Chapter 2: Fault-Tolerant Design -- Special nodes -- Arbiters -- Hidden secondary -- Delayed secondary -- Partial restores -- Nonvoting secondary -- Avoiding failure -- Points of failure -- Reserve capacity -- Automatic failover -- Designing for flexibility -- DNS not IP -- Auto-discovery -- Planned downtime
|
| 505 |
0 |
|
|a Multiple routers -- Rolling maintenance -- Clean step-down -- Tooling failover -- Failure scenarios -- Network partition -- Hardware failure -- Remote DC failure -- Storage volume failure -- Network degradation -- Shared VM hosts -- Shared storage area network -- Unbalanced hardware -- Key takeaways -- Chapter 3: Security -- Local access -- Network hardening -- Firewalls with iptables -- Limit interfaces with bindIp -- Customize ports -- Filesystem -- Authentication -- Passwords vs. keyfiles -- Connecting with passwords -- Keyfiles -- x.509 certificates -- Client authentication
|
| 505 |
0 |
|
|a Intro -- Table of Contents -- About the Author -- About the Technical Reviewer -- Acknowledgments -- Chapter 1: Core Concepts -- Key features of MongoDB -- Differences to "traditional databases" -- Terminology -- Storage engines -- Binary JSON -- Data files -- Concurrency -- Relationships -- Referential integrity -- ACID compliance -- Atomicity -- Consistency -- Isolation -- Bulk operations -- Durability -- Journal and flushing -- Scaling -- Replication -- Syncing -- Elections -- Lag/staleness -- Oplog window -- Read preference -- States -- Sharding -- Chunks -- Choice of shard key
|
| 505 |
0 |
|
|a Custom redaction -- Right to be forgotten -- Product guarantees -- Avoid dated collections -- Data flows -- Processing data -- End-to-end data encryption -- Data storage -- Data mapping -- Auditing changes -- Validation -- Pseudonymization -- Generalizing data -- Encryption at rest -- Backups -- Regulations around the world -- US healthcare -- California -- India -- Canada -- China -- Russia -- Design recommendations -- Field-level encryption -- Views -- Separate permissions -- Data leaks -- Sharding -- Logging -- Minimize vulnerabilities -- Summary -- Chapter 5: Basic Topologies -- Introduction
|
| 653 |
|
|
|a MongoDB / fast
|
| 653 |
|
|
|a Bases de données / Gestion
|
| 653 |
|
|
|a Open source software / fast
|
| 653 |
|
|
|a Computers / Database Management / General / bisacsh
|
| 653 |
|
|
|a Open source software / http://id.loc.gov/authorities/subjects/sh99003437
|
| 653 |
|
|
|a Bases de données orientées objet
|
| 653 |
|
|
|a Object-oriented databases / http://id.loc.gov/authorities/subjects/sh88007927
|
| 653 |
|
|
|a Object-oriented databases / fast
|
| 653 |
|
|
|a Database management / http://id.loc.gov/authorities/subjects/sh85035848
|
| 653 |
|
|
|a Logiciels libres
|
| 653 |
|
|
|a Databases / bicssc
|
| 653 |
|
|
|a MongoDB. / http://id.loc.gov/authorities/names/no2011130709
|
| 653 |
|
|
|a Database management / fast
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 500 |
|
|
|a Includes index
|
| 015 |
|
|
|a GBC0H5287
|
| 776 |
|
|
|z 9781484258163
|
| 776 |
|
|
|z 1484258169
|
| 776 |
|
|
|z 9781484258170
|
| 776 |
|
|
|z 1484258177
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781484258170/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 658
|
| 082 |
0 |
|
|a 005.757
|
| 520 |
|
|
|a Create a world-class MongoDB cluster that is scalable, reliable, and secure. Comply with mission-critical regulatory regimes such as the European Unions General Data Protection Regulation (GDPR). Whether you are thinking of migrating to MongoDB or need to meet legal requirements for an existing self-managed cluster, this book has you covered. It begins with the basics of replication and sharding, and quickly scales up to cover everything you need to know to control your data and keep it safe from unexpected data loss or downtime. This book covers best practices for stable MongoDB deployments. For example, a well-designed MongoDB cluster should have no single point of failure. The book covers common use cases when only one or two data centers are available. It goes into detail about creating geopolitical sharding configurations to cover the most stringent data protection regulation compliance. The book also covers different tools and approaches for automating and monitoring a cluster with Kubernetes, Docker, and popular cloud provider containers. You will: Get started with the basics of MongoDB clusters Protect and monitor a MongoDB deployment Deepen your expertise around replication and sharding Keep effective backups and plan ahead for disaster recovery Recognize and avoid problems that can occur in distributed databases Build optimal MongoDB deployments within hardware and data center limitations
|