2022 MongoDB World Final

MongoDB
arc beats above · slides in the middle · loops below · scroll → 2 LOOPS
SETUP TENSION ANALYSIS EVIDENCE RESOLUTION APPENDIX
HOVER FOR DETAILS · CLICK A SLIDE FOR FULLSCREEN · STEP 5
No image bound to this slide. Wire up imgproxy to display the rendered slide JPEG.

Deck intelligence map

4
coverage by narrative range · generated from this deck JSON

Slide inventory

67
every slide · same image gating as the playbook
01
Slide 1
front_matter
Open slide detailBeat · Situation & Context
02
establish_context
Open slide detailBeat · Situation & Context
03
size_opportunity
Open slide detailBeat · Situation & Context
04
transition
Open slide detailBeat · Situation & Context
05
The slide uses a visual metaphor of software categories (CRM, ERP, P2P) to represent the market landscape.frame_problem
Open slide detailBeat · Situation & Context
06
The visual uses a grid of boxes to represent workloads, with one highlighted to illustrate the concept.frame_problem
07
summarize
08
present_solution
09
transition
10
summarize
11
summarize
12
summarize
13
transition
14
analyze_data
15
transition
16
summarize
Open slide detailBeat · Problem & ComplicationLoop · Tale Two Worlds
17
frame_problem
Open slide detailBeat · Problem & ComplicationLoop · Tale Two Worlds
18
frame_problem
Open slide detailBeat · Problem & ComplicationLoop · Tale Two Worlds
19
summarize
Open slide detailBeat · Problem & ComplicationLoop · Tale Two Worlds
20
summarize
Open slide detailBeat · Solution & ApproachLoop · Tale Two Worlds
21
The slide uses a dark green background with a leaf icon in the top right corner, typical of MongoDB branding.present_solution
Open slide detailBeat · Solution & ApproachLoop · Cost Of Inaction
22
present_solution
Open slide detailBeat · Solution & ApproachLoop · Cost Of Inaction
23
summarize
Open slide detailBeat · Solution & Approach
24
state_next_steps
Open slide detailBeat · Solution & Approach
25
present_solution
Open slide detailBeat · Solution & Approach
26
The slide uses a collage of various time-series data visualizations (charts, logs, financial tickers) to demonstrate the ubiquity of the data type.establish_context
27
frame_problem
28
summarize
29
summarize
30
The slide uses a horizontal timeline to categorize technical improvements by software version.summarize
31
present_solution
32
establish_context
33
The slide uses a hub-and-spoke style diagram to show the data flow between an application, a database, and a search engine, emphasizing the 'Sync/ETL' bottlenecframe_problem
34
The diagram illustrates the architectural simplification of using Atlas Search compared to traditional separate search/database setups.present_solution
35
The slide uses a 3x3 grid layout to categorize different industry verticals and their specific applications.illustrate_case
36
summarize
37
present_solution
38
establish_context
39
summarize
40
The slide uses a split-screen layout to contrast two different use cases for the same technology.illustrate_case
41
present_solution
42
The slide uses a dark theme with green accents, typical of MongoDB branding.present_solution
43
summarize
44
The diagram illustrates a disconnect between the operational data layer (Atlas) and the end-user roles (Analysts, Engineers, Scientists) who require real-time aframe_problem
45
present_solution
46
summarize
47
The slide uses a simple three-column layout to categorize strategic focus areas.present_solution
48
The slide uses a step-like diagram to illustrate the progression of abstraction layers in software development.present_framework
49
transition
50
compare_options
51
compare_options
52
compare_options
53
summarize
54
present_solution
55
summarize
56
frame_problem
57
present_solution
58
summarize
59
cite_precedent
60
summarize
61
present_solution
Open slide detailBeat · Impact & Next Steps
62
The slide uses a quote-like structure to convey a core value proposition.summarize
Open slide detailBeat · Impact & Next Steps
63
The diagram depicts a highly fragmented data architecture with numerous ETL and sync processes connecting various database types (RDBMS, Key-Value, Wide Column,frame_problem
Open slide detailBeat · Impact & Next Steps
64
Uses parallel structure and anaphora to emphasize the negative impact across different roles.frame_problem
Open slide detailBeat · Impact & Next Steps
65
The pendulum represents market sentiment or adoption shifting between two poles.establish_context
Open slide detailBeat · Impact & Next Steps
66
The diagram uses a layered isometric approach to represent the stack: top layer (data models), middle layer (interface/workloads), bottom layer (deployment/infrsummarize
Open slide detailBeat · Impact & Next Steps
67
summarize
Open slide detailBeat · Impact & Next Steps