DNS - Deepstash
Product Management Starter Kit

Learn more about computerscience with this collection

How to focus on the present moment

How to cultivate empathy and understanding towards others

How to set personal and professional goals

Product Management Starter Kit

Discover 28 similar ideas in

It takes just

4 mins to read

DNS

  • DNS stands for “Domain Name System” and it’s a backbone technology that makes the world wide web possible. 
  • At the most basic level DNS provides a key/value lookup from a domain name (e.g., google.com) to an IP address (e.g., 85.129.83.120), which is required in order for your computer to route a request to the appropriate server. 
  • Analogizing to phone numbers, the difference between a domain name and IP address is the difference between “call John Doe” and “call 201-867–5309.” Just like you needed a phone book in the old days, you need DNS to look up the IP address for a domain. 

3

5 reads

MORE IDEAS ON THIS

Full-text Search Service

It leverages an inverted index to quickly look up documents that contain the query keywords.

The most popular Full-Text search platform today is Elasticsearch though there are other options such as Sphinx or Apache SOLR. 

Full-text search leverages an inverted index to quickly look up...

3

2 reads

Data

Today, companies live and die based on how well they harness data. Almost every app these days, once it reaches a certain scale, leverages a data pipeline to ensure that data can be collected, stored, and analyzed. A typical pipeline has three main stages:

  1. The app sends data, typically...

3

4 reads

Job Queue & Servers

  • Job queues store a list of jobs that need to be run asynchronously. The simplest are first-in-first-out (FIFO) queues though most applications end up needing some sort of priority queuing system. Whenever the app needs a job to be run, either on some sort of regular schedule or as determined...

3

2 reads

Caching Service

A caching service provides a simple key/value data store that makes it possible to save and lookup information in close to O(1) time. 

Applications typically leverage caching services to save the results of expensive computations so that it’s possible to retrieve the results from the cache ...

3

2 reads

Load Balancer

They’re the magic sauce that makes scaling horizontally possible. They route incoming requests to one of many application servers that are typically clones/mirror images of each other and send the response from the app server back to the client. 

Any one of them should process the request t...

3

4 reads

Services

Once an app reaches a certain scale, there will likely be certain “services” that are carved out to run as separate applications. 

They’re not exposed to the external world but the app and other services interact with them. 

3

1 read

Parting thoughts

And that’s a wrap on Web Architecture 101. I hope you found this useful. I’ll hopefully post a series of 201 articles that provide deep dives into some of these components over the course of the next year or two. 

3

5 reads

Web Application Servers

At a high level, web application servers are relatively simple to describe. They execute the core business logic that handles a user’s request and sends bac HTML to the user’s browser. 

To do their job, they typically communicate with a variety of backend infrastructures such as databases, ...

3

2 reads

Database Servers

Every modern web application leverages one or more databases to store information. Databases provide ways of defining your data structures, inserting new data, finding existing data, updating or deleting existing data, performing computations across the data, and more.

In most cases the web...

3

2 reads

11. CDN

The technology provides a way of serving assets over the web much faster than serving them from a single origin server. It works by distributing the content across many "edge" Servers around the world. In general a web App should always use a CDN to serve CSS, Javascript, images, videos.

3

4 reads

CURATED FROM

IDEAS CURATED BY

linholme

Engineer/ technical sales

Related collections

Other curated ideas on this topic:

Username vs Email Address

Summary: 

The Difference Between Username and Email Address is that user name is a unique combination of characters, such as letters of the alphabet and/or numbers, that identifies a specific user. 

While just as you address a letter ...

The REST architectural style is designed for client-server applications. The coupling between the client and the server must be as loose as possible to facilitate large-scale adoption. This is achieved by creating a layer of abstraction on the server by defining resources that encapsulate entitie...

The most common things most services presume users have ready access to

  • A phone number
  • A bank account or credit/debit card
  • An email address
  • Official identification, such as passport, driving licence or state-issued ID card
  • An address, or proof of address
  • Any of the above, in the country that you’re operating in
  • Any...

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Personalized microlearning

100+ Learning Journeys

Access to 200,000+ ideas

Access to the mobile app

Unlimited idea saving

Unlimited history

Unlimited listening to ideas

Downloading & offline access

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates