DEV Community: Daniel Philip Johnson

Fundamentals of Document Databases

Daniel Philip Johnson — Mon, 20 Oct 2025 08:58:54 +0000

Scary word alert

NoSQL = "Not only SQL," represents a category of database systems that deviate from traditional relational databases

Introduction

In this blog, we will delve into the fundamentals of document databases, a type of NoSQL database. By comparing document databases to a house with various rooms, we'll explore their document-oriented structure, primary and standard fields, and the key terminology associated with them.

Document Database: The House of Data

Imagine a document database as a house, acting as a container that accommodates different rooms, represented by different document collections. We can define separate room documents for essential areas like "Bedrooms," "Bathrooms," "Living Room," and "Kitchen.”

Document-Oriented Structure: Organizing Data

A document-oriented structure serves as the data model in document databases, allowing the organization and storage of data in the form of self-contained documents. Each document represents a unique entity or object, encompassing all the relevant data associated with it. Consider a room as an example, with fields like roomName, size, flooring, and furniture, encapsulated within a document. To illustrate this concept, let's consider a room as an example:

room {
   _id: ObjectId("1234567890abcdef12345678")
   roomName: “bedroom”,
   size: “12 feet”,
   flooring: "wood",
   furniture:["wardrobe", "bed"]
}

In this example, we have a room document that possesses a unique identifier (_id) assigned by the database. It includes descriptive attributes such as the room's name ("bedroom"), size ("12 feet"), flooring type ("wood"), and an array of furniture items, including a wardrobe and a bed. This self-contained structure allows for efficient storage and retrieval of room-specific data within the document database.

Primary Fields and Standard Fields: Defining Document Structure

In our pursuit of an efficient document structure, let's delve into the essential fields that compose a room document.

Firstly, we have the primary key, a vital component that plays a pivotal role in document identification and retrieval. This unique identifier holds great significance, especially when accessing documents through APIs such as api/room/1234567890abcdef12345678. Additionally, the primary key enforces uniqueness, ensuring that no duplicate documents are created within the collection. Moreover, it enables the creation of indexes, facilitating swift and direct retrieval of specific documents based on their distinctive identifiers. Fortunately, MongoDB automates the generation of primary keys, relieving you of the burden of creating them manually.

However, you also have the flexibility to define your own primary key if you possess a field guaranteed to be unique. For instance, in the case of books, the International Standard Book Number (ISBN) serves as an excellent candidate. Consider the following example:

book {
   _id: "978-0-123456-78-9",
   author: "author",
   title: "the title"
}

Alongside the primary key, we incorporate several standard fields which are made up of attributes and values to comprehensively define our room document structure. These fields include:

roomName: Designates the name of the room, allowing easy identification.
size: Specifies the size of the room, providing relevant information about its dimensions.
flooring: Describes the type of flooring used in the room, adding to its aesthetic and functional attributes.
furniture: Represents an array that captures the furniture items present in the room, facilitating an inventory-like perspective.

By thoughtfully incorporating these primary and standard fields into our document structure, we establish a foundation for efficient storage, retrieval, and organization of room-specific data within our MongoDB document database.

Value Types: Diverse Data Representation

As you explore the fields in our collection, you might have noticed the presence of strings and arrays. However, it's important to understand that document databases like MongoDB offer a wide range of value types to cater to diverse data requirements. Typically, these databases support popular data formats such as JSON or BSON.

In MongoDB, you have the flexibility to utilize various value types for your fields. Let's explore some of the commonly used value types:

String: Represents a sequence of characters, allowing you to store textual information.
Number: This can be either an integer or a floating-point number, enabling you to store numerical data.
Boolean: Represents true or false values, providing a binary data type for logical operations.
Date: Stores date and time values, facilitating the storage of temporal information.
Array: Allows you to store an ordered list of values, providing a convenient way to group related data elements together.
Object: Represents a collection of key-value pairs, enabling you to store complex and structured data.
Null: This represents the absence of a value, allowing you to indicate the lack of data in a field.
ObjectId: A special data type commonly used as a unique identifier for documents, providing an automatically generated identifier within MongoDB.
Timestamp: A BSON data type that represents a 64-bit timestamp, facilitating the tracking of time-related information.
Binary Data: Enables the storage of binary information, such as images or files, within the database.

By leveraging these diverse value types, document databases empower you to effectively store and manipulate data with flexibility and precision. Whether you need to capture textual, numerical, temporal, or structural information, MongoDB offers a comprehensive set of value types to accommodate your data needs.

Now we should have a much clearer understanding of all the pieces that make up a document DB.

Key Terminology: Understanding the Basics

To wrap up, let's review key terminology:

Document database: A NoSQL database that stores and manages data in self-contained documents.
Document collection: A grouping of related documents, acting as a logical unit for organization and management.
Document-oriented structure: The data model used in document databases, organizing data into self-contained documents.
Primary field: The unique identifier or primary key for a document within a collection, facilitating identification and retrieval.
Standard field: Predefined fields within a document structure that capture specific attributes or properties.
Attribute: A characteristic or property of an entity, defining the fields or properties within a document.
Value: The actual data stored within an attribute or field of a document.

By understanding these key concepts, you'll gain a solid foundation in the fundamentals of document databases and be better equipped to work with them effectively.

From Linear to Systems Thinking: Solving Complex Tech Challenges

Daniel Philip Johnson — Mon, 20 Oct 2025 08:53:02 +0000

Introduction

Former President Barack Obama once remarked, “In my job, I wind up dealing with problems that are both messy and complicated. By the time a problem reaches my desk, it’s one that nobody else has been able to solve.” This quote highlights a critical reality faced by many in technology today: the most challenging problems are often complex, lacking clear-cut solutions. As technology evolves, so too does the complexity of the challenges we face.

Traditional problem-solving methods, like linear thinking, often fall short when dealing with these intricate issues. Instead, systems thinking—a holistic approach—offers a more effective way to navigate and resolve them. In this blog, we’ll explore the journey from linear to systems thinking, focusing on why it’s crucial for anyone involved in the tech industry. By the end, you’ll see how embracing systems thinking can help you create better solutions, spark innovation, and improve team dynamics in your work.

1. Understanding Linear Thinking

a. What is Linear Thinking?

Linear thinking is a simple, step-by-step way of solving problems. Think of it as following a recipe: you start at point A, follow the instructions in order, and arrive at point B. Each step builds logically on the previous one, and there’s a clear cause-and-effect relationship throughout the process.

b. Examples of Linear Thinking in Tech

Coding Logic: In coding, developers often use “if-then” statements, where one action leads to a specific result. For example, “If this happens, then that will happen.”
Project Planning: Traditional project management follows a linear sequence of tasks. One task is completed before moving on to the next, assuming each step must be done in a certain order.

c. Why is Linear Thinking Common?

From an early age, we are taught to break down problems into smaller, manageable parts—this method is called reductionism. It simplifies complex issues by focusing on individual components rather than the whole.

d. Benefits of Linear Thinking

Predictability: Linear thinking gives a clear roadmap, making outcomes easier to predict.
Simplicity: It’s easy to communicate and understand, which helps with planning and execution.
Effective for Simple Problems: For straightforward issues, linear thinking works well.

2. Limitations of Linear Thinking

a. Missing the Bigger Picture

When we focus only on individual components, we risk missing how everything fits together. This can hurt the overall system. For example, optimizing one feature of a product without considering the user experience as a whole can lead to a disjointed result.

b. Reductionism vs. Holism

Reductionism: This approach breaks down complex systems into smaller parts, assuming that understanding each part leads to understanding the whole.
The Challenge: In complex systems, reductionism can overlook how parts interact with each other. A system’s behavior often emerges from the relationships between its parts, which aren’t visible when looking at individual components.
Holism: Holism, on the other hand, focuses on the entire system, understanding how different elements work together.

c. Impact on Complex Systems

Software Systems: Changing one part of a large software system might affect other areas in unexpected ways. Linear thinking might not catch these ripple effects.
Organizational Impact: Implementing a new policy without considering how it affects different departments can lead to operational issues.
Unpredictability: In systems with many interacting components, linear models often fail to predict outcomes accurately.

3. Introduction to Systems Thinking

a. What is Systems Thinking?

Systems thinking is a way of understanding a system by looking at how all the parts are connected. Instead of isolating individual components, it focuses on relationships, patterns, and interactions. This holistic view helps to grasp the complexity of the system as a whole.

b. Linear vs. Nonlinear Thinking

Linear Thinking: Think of it as following a straight road—each step leads logically to the next.
Nonlinear Thinking: It’s more like navigating a maze, where small changes can lead to unexpected outcomes. Nonlinear systems are less predictable, and a minor adjustment in one area can cause significant effects elsewhere.

c. Why It’s Important in Technology

In tech, we often work with complex systems where different components interact in unpredictable ways. Systems thinking is essential because it helps to:

Understand Interactions: See how different elements influence each other.
Encourage Innovation: Look beyond the obvious to find new solutions.
Adapt to Change: Systems thinking helps anticipate and respond to changes in the system more effectively.

4. Nonlinear Thinking in Practice

a. Nonlinear Relationships

In nonlinear systems, cause and effect don’t always match up in a predictable way. Small changes in one area can lead to major shifts elsewhere. Understanding these relationships is critical for problem-solving.

b. Examples in Technology

Software Development: Fixing a small bug in one part of the code can unexpectedly cause issues elsewhere in the system.
Network Systems: An increase in users can create network congestion, slowing down the system or causing crashes.
Cybersecurity: Patching one vulnerability might open up another if the overall system isn’t considered.
Artificial Intelligence: AI models trained on specific data can behave unpredictably when exposed to new information.
Social Media Algorithms: Tweaking an algorithm can unexpectedly change what content goes viral, altering user engagement and platform dynamics.

c. The Ripple Effect

Minor actions can have far-reaching consequences. For example, a small change to a website’s user interface might confuse users, leading to decreased engagement and lower revenue. Understanding these ripple effects is a key part of systems thinking.

5. Key Principles of Systems Thinking

a. Seeing the Whole

It’s important to understand how each component fits within the system. This perspective ensures that changes benefit the entire system, rather than optimizing just one part.

b. Interconnections

Exploring Relationships: Look at how different elements interact. For instance, a software update might improve performance but cause compatibility issues with other applications.
Example: When a new feature is added, how does it affect the overall user experience? Thinking holistically helps avoid unintended consequences.

c. Patterns Over Time

Identifying Trends: Look for patterns and recurring issues over time. These can highlight deeper problems that need to be addressed.
Data Analytics: Monitoring system performance and user behavior can help predict future trends.

d. Feedback Loops

Positive Feedback Loops: These amplify changes. For example, more users can attract even more users due to network effects.
Negative Feedback Loops: These help maintain stability. For example, load balancing prevents server overload.
Example: User feedback leads to product improvements, which in turn boosts user satisfaction and generates more feedback.

e. Embracing Complexity and Uncertainty

Acceptance: Not all variables can be controlled or predicted.
Preparation: Have flexible strategies to adapt to unexpected changes.

f. Collaborative Approach

Cross-Functional Teams: Work with other departments to get diverse perspectives.
Communication: Sharing insights helps teams understand the bigger picture.

g. Root Cause Analysis

Beyond Symptoms: Focus on finding the root causes of problems, rather than just treating symptoms.
Tools: Techniques like the “5 Whys” can help uncover the deeper issues at play.

6. The Importance of Systems Thinking in Tech

a. Managing Complex Software Systems

Systems thinking leads to better software architecture by considering how different parts interact. This approach reduces integration issues and makes the system more scalable.

b. Anticipating and Mitigating Risks

By understanding the system’s interconnectedness, potential points of failure can be identified and addressed proactively, minimizing downtime.

c. Encouraging Innovation

Looking at the bigger picture helps teams explore unconventional solutions. This can lead to breakthrough innovations and a competitive edge.

d. Improving Team Dynamics

When teams see how their work fits into the bigger picture, they collaborate more effectively. This leads to improved efficiency and morale.

7. Transitioning from Linear to Systems Thinking

a. Challenges in Changing Mindsets

Comfort Zones: We’re used to linear thinking because it’s what we’ve learned.
Complexity Aversion: Systems thinking can feel overwhelming because it’s more complex and doesn’t offer easy answers.

b. Developing Systems Thinking

Continuous Learning: Explore books, courses, and seminars on systems thinking.
Practical Application: Start small by applying systems thinking principles to everyday projects.
Mentorship: Learn from people who already practice systems thinking.
Reflection: Regularly review your decisions and their impact on the overall system.

c. Tools for Systems Thinking

Systems Mapping: Create visual maps to understand the components and relationships within a system.
Causal Loop Diagrams: Show how different elements of a system influence one another.
Simulation Models: Use software to simulate system behavior under various scenarios.

Conclusion

As President Obama pointed out, the hardest problems are often the most complex. While linear thinking is useful for straightforward problems, it often falls short in today’s interconnected world. Systems thinking provides the tools to tackle these challenges by seeing the bigger picture.

By adopting systems thinking, you’ll foster better collaboration, anticipate risks, and drive innovation within your team. As modern tech challenges grow more complex, systems thinking becomes not just a tool, but a necessity.

Embrace systems thinking and see how it can revolutionize the way you approach complex problems in tech. Start by observing the connections in your current projects, applying a holistic view, and encouraging your team to think beyond isolated solutions. By taking a step back to see the bigger picture, you’ll drive innovation, improve your decision-making, and help your team thrive in today’s fast-paced, interconnected world.

About the Author

As someone who applies these principles in my work, I’ve experienced how impactful they can be in building scalable solutions. If you’d like to explore more of my approach and connect with me, here's a bit about who I am:

I'm Daniel Philip Johnson, a senior frontend engineer specializing in frontend development and architecture. I’m passionate about simplifying complex challenges and building scalable, innovative solutions. To explore more of my work, visit my personal website, or connect with me on LinkedIn for insights on tech leadership and the future of frontend development.

Monthly reflection - April 2021

Daniel Philip Johnson — Sat, 01 May 2021 13:03:26 +0000

Introduction

Every month as a frontend engineer, I reflect on what I have achieved. Let's talk about April 2021. In summary, I took a significant risk and left my second job. It's something I felt I had to do. My mindset was off and I wanted to focus on writing and improving with front end development. I regathered my thoughts and made a plan of action to further my skills and finally, I have committed to a content creation schedule.

Here is what I have done 👨‍💻

Read News Articles 📰

Here are my top 5 articles I have read this month. My main focus as a frontend engineer is React and Js. So the articles I have included will be based on these topics.

Recently, I started to co-author a book for a publisher.

Writing a book is something I'm excited to be doing. I wish I could tell everyone what it is I'm writing. For now, it has to be a secret 😏 . Hint* It's front-end related. Surprisingly, I have enjoyed co-writing two chapters, and I learnt something valuable. By writing about a topic, you are testing your knowledge and identifying possible gaps. I have started to improve immensely and, my recall is so much better. For this reason, I have started to pursue writing articles and helpful blogs. If you haven't written a blog article, I encourage you to do it!

Courses I am taking 👨🏻‍🎓🎓

In this section, I will list the courses I am currently taking. I will also include courses I have finished and write personal reviews listing what I have learnt.

Mastering the Coding Interview: Data Structures + Algorithms (ongoing)
Understanding TypeScript - 2021 Edition: (ongoing)

Videos I watched 🎥

The focus this month was slightly geared towards encryption. In pursuit of bettering my skills, I started to use SSH. During my time learning, I documented it by writing an article on how to use SSH and how it worked.

Secret Key Exchange (Diffie-Hellman) Computerphile
Diffier-Hellman - the Mathematics bit Computerphile
Key Exchange-Problems - Computerphile
Elliptic-Curves - Computerphile
Rendering performance inside out - Martin Splitt

Amazon project 💼

In summary, my amazon clone is close to having an alpha release. My main focus this month is to implement searching functionality.

What features I added this month.

I integrated stripe payment with a custom strapi controller. The reason for this was to calculate the cart on the backend.
Currently, a user can put an item in a cart and checkout.
Multiple items added to the cart change the quantity
Made a react portal to display error messages or success messages
All pages were styled to mirror the amazon website.

From this point onwards I plan to make a blog article each month related to my project progress and how I implemented features.

What I did wrong 🙄

I allowed leaving my job to affect my focus. I became torn about the situation but eventually realised that sometimes you need to decide for yourself. I discovered that being nice doesn't mean you have to say yes. Always consider your feelings too. Sometimes you need to put yourself first. Now that it is all done. I'm ready for my next chapter 😀.

What I accomplished ⏳

In April, I feel like I did not accomplish as much as I would have intended. There were a few moments I felt slightly confused and wondered what would become of me. Not long after, I started to plan my next chapter. I reflected on my frontend abilities and soft skills. I decided on what I need to improve and how to achieve it.

Thank you for reading 👋

For now, I am just publishing my blogs to dev.to. In the future, I will look to expand to more blogging platforms and will start to host my blogs on my website. If you enjoy my blogs, you might also be interested in my tweets on my Twitter. Please feel free to share a tweet with #monthlyreflection, tag me and tell me about your month.