This document summarizes the key steps involved in processing a web request from a browser to a server and back. It discusses the TCP/IP protocol suite which handles packaging and transmission of data, URLs which identify web resources, HTTP which is the protocol for requesting and receiving web pages, web caching for reusing stored resources, DNS which translates domain names to IP addresses, TCP connections for transmitting data between devices, and the response from applications on web servers. The document also provides information about career opportunities at Google, focusing on engineering roles.

1. Life of a request
Ana Oprea
Rails Girls Munich
13.06.2015

2. Contents
● Internet Protocol suite (TCP/IP)
● URLs
● HTTP
● Web caching
● DNS
● TCP connection
● Your Application
---------------------------------------------------------------------------------------------------------
● Opportunities at Google
2

3. Internet Protocol suite (TCP/IP)
End-to-end connectivity
● packaging
● addressing
● transmission
3source

4. URLs
Uniform Resource Locator
//<user>:<password>@<host>:<port>/<url-path> ? <parameter=value>
● https: // www.google.de / ? q=rails+girls+munich+2015
● http: // railsgirls.com / munich2015
● ftp: // foo : bar @ myhost.com /
● mailto : anaoprea @ google.com
● file: // /home/anaoprea/Documents/note12345.txt
4

5. HTTP
HyperText Transfer Protocol
Browser: "Ok, so, I have a user
requesting this address: railsgirls.
com. I figure since there are no
slashes or anything, this is a direct
request of a main page. There was
also no protocol or port defined, so I'll
assume it's HTTP and going to port
80..."
5
source

6. Web caching
Reusing previously stored resources
6
cc source
source

7. DNS
Hierarchical distributed Domain Name
System
Browser: "oh well, first things first. Hey
DNS, pal, wake up! Where is this
railsgirls.com hiding at?"
DNS: "Right... wait a sec, I'll ask the
ISP servers. Ok, it looks like
109.74.202.152"
7
source

8. TCP connection
8source

9. Your application
9
source

10. The Reply
10
source

11. Resources
● Rails Girls Guides: Web Fundamentals
● Question: What exactly happens when you type browse a website in your
browser
● TCP/IP (Wikipedia)
11

12. Opportunities at Google
http://www.google.com/about/careers/teams/
12
Engineering &
Design
Operations &
Support
Product
Management
Developer Relations &
Technical Solutions
Sales & Account
Management
Product &
Customer
Support
Partnerships Sales Operations
Administrative Business
Strategy
Finance Legal & Government
Relations
Marketing &
Communications
People
Operations
Real Estate &
Workplace
Services
Social Impact

13. Engineering and Design
http://www.google.com/about/careers/teams/engineering/
“Google is and always will be an engineering company. We hire people with a
broad set of technical skills who are ready to tackle some of technology’s
greatest challenges and make an impact on millions, if not billions, of users. At
Google, software, hardware, network, test and site reliability engineers not
only revolutionize search, they routinely work on massive scalability and
storage solutions, large-scale applications and entirely new platforms for
developers around the world. From AdWords to Chrome, Android to
YouTube, Social to Local, Google engineers and designers are changing the
world one technological advance after another.”
Check out Google Munich ;) https://www.google.
com/about/careers/locations/munich/ 13