Home
Explore
Exams
Search for anything
Login
Get started
Home
ITEC 4020 - L4: Web Services (Concepts)
ITEC 4020 - L4: Web Services (Concepts)
0.0
(0)
Rate it
Studied by 0 people
Call with Kai
Knowt Play
Learn
Practice Test
Spaced Repetition
Match
Flashcards
Card Sorting
1/20
There's no tags or description
Looks like no tags are added yet.
Study Analytics
All Modes
Learn
Practice Test
Matching
Spaced Repetition
Name
Mastery
Learn
Test
Matching
Spaced
No study sessions yet.
21 Terms
View all (21)
Star these 21
1
New cards
Web Service
A software system that enables machine-to-machine communication over a network using standardized protocols like HTTP/HTTPS.
2
New cards
Key Traits of Web Services
Platform-independent, interoperable, loosely coupled, and use standardized protocols.
3
New cards
Purpose of Web Services
Allow application integration, reusability, interoperability, and scalability.
4
New cards
Application Integration
Web services connect different systems, such as linking inventory systems with sales systems.
5
New cards
Reusability
A single web service can be reused by multiple applications, like a shared payment API.
6
New cards
Interoperability
Web services allow different platforms and programming languages to work together.
7
New cards
Scalability
Web services can be distributed across multiple servers to handle more users or requests.
8
New cards
Real-World Examples of Web Services
APIs like OpenWeatherMap (weather), Google Maps, PayPal/Stripe (payments), and “Sign in with Google.”
9
New cards
Request-Response Model
The client sends an HTTP request, the server processes it, and replies with a response.
10
New cards
HTTP Request Contains
Method (GET, POST, etc.), URL, headers, and optional body.
11
New cards
HTTP Response Contains
Status code (200, 404), headers, and body (data or error message).
12
New cards
Stateless Communication
Each request is independent, with no memory of previous interactions; default in HTTP.
13
New cards
Stateful Communication
The server maintains context across multiple requests, remembering session data.
14
New cards
Advantage of Stateless Communication
Makes scaling and load balancing easier since no session data is stored on the server.
15
New cards
Advantage of Stateful Communication
Allows features like login sessions or remembering user data across requests.
16
New cards
Examples of Stateful Protocols
Protocols like FTP, Telnet, or traditional database connections.
17
New cards
Cookies
A small piece of client-side data sent with each request to help maintain state in stateless HTTP.
18
New cards
Tokens (JWTs)
A client-stored authentication token sent with requests to maintain secure state.
19
New cards
URL Parameters
Information added to the query string of a URL to carry session or state data.
20
New cards
Custom Headers
Headers added to HTTP requests that carry state information like authentication tokens.
21
New cards
Booking API Example
In a movie booking service, the client POSTs with a token and data, the server validates and processes, and replies with confirmation.