"How it all works"

"How it all works"

Introduction to the Rails Girls web-app. Including some info on backend - frontend.

3a912a3965cdee320eb270e2a8acc170?s=128

Lieke22

June 20, 2019
Tweet

Transcript

  1. How it all works Introduction to Web Apps

  2. About me: - Work in Tech, but I have a

    master degree in History - Big Rails Girls fan <3 - I work at GitHub - I’m not a developer - @lieke2208
  3. Today you’re going to build a web app!

  4. But how does this work?

  5. The Internet: “The large system of connected computers around the

    world that allows people to share information and communicate with each other” - Cambridge Dictionary
  6. CLIENT ←→ INTERNET ←→ SERVER
 Browser “Browsers download websites from

    web servers (or "application servers") using the HTTP protocol (a protocol, in the realm of programming, is a universally known data format and sequence of steps enabling communication between two parties). The HTTP protocol is based on a request-response model. The client (your browser) requests data from a web application that resides on a physical machine. The web application, in turn, responds to the request with the data your browser requested.” How does this work?
  7. It is like a Restaurant CUSTOMER ←→ WAITER ←→ CHEF


    Menu This idea coming from Rodrigo Hänggi and I liked the explanation so much that I’m using it here. All props go to @therod, who shared this at Rails Girls Vienna. https://speakerdeck.com/therod/ programming-101
  8. Scenario in the restaurant You tell the WAITER that you

    would like a DISH by pointing on the MENU. The WAITER delivers your request to the CHEF. They start preparing your DISH and then send it back through the WAITER again.
  9. Scenario Internet You tell the INTERNET that you would like

    a PAGE by pointing in the BROWSER. The INTERNET delivers your request to the SERVER. It start preparing your PAGE and then sends it back through the INTERNET again.
  10. But what is a web application? Web applications act like

    chefs they: ➢ Take requests ➢ Do something with them ➢ Send the results back You tell them how they behave and what they need to do.
  11. Web pages can be static or dynamic.

  12. How does a web app work?

  13. Web app consists of a front-end & back-end The front-end

    developer is responsible for the part that you see and interact in the Web app. They have an in-depth knowledge of three languages: - HTML: the bones of a page structure, required in every website that you visit. - CSS: Cascading Style Sheets, is what gives a better look to the HTML. Making it possible to include colors, fonts & images. - Javascript: last piece of the magic that will make all the interactions and animations turning into a full Web application. The back-end of a website consists of a server, an application, and a database. A back-end developer builds and maintains the technology that powers those components which, together, enable the user-facing side of the website to even exist in the first place. In order to make the server, application, and database communicate with each other, back-end devs use server-side languages like PHP, Ruby, Python, Java, and .Net to build an application, and tools like MySQL, Oracle, and SQL Server to find, save, or change data and serve it back to the user in front-end code.
  14. None
  15. Ruby on Rails - A web application framework written in

    Ruby - Ruby = a general purpose programming language. - Invented by Yukihiro Matsumoto. - My opinion: beginner friendly
  16. None
  17. Ruby on Rails web framework - Written in Ruby -

    Set of functionality to help write web applications - Is designed to make programming web applications easier by making assumptions about what every developer needs to get started - Rather than having to write every single line of code in a program from scratch, Rails already gives you the framework to get started.
  18. Time to start building!