-
Notifications
You must be signed in to change notification settings - Fork 39
Expand file tree
/
Copy pathsession-10.txt
More file actions
137 lines (101 loc) · 2.55 KB
/
Copy pathsession-10.txt
File metadata and controls
137 lines (101 loc) · 2.55 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
Root servers
13 root servers across the world managed by different organisations and goverments to control TLD's and part of ICANN. DNS resolutions requests from ISP comes to root servers
TLD
Top level domains, basically who sells the domains. It has the complete details of the domains booked, avaialalbe, buyer information, etc.
Registars
Who sells the domains, basically mediators between TLD and end users. Who can manage the domain too
NS
Who is currently managing the domain, we can buy domain with one registar and we can transfer the management to another registar by updating NS records.
A record is mapping the IP address to domain
db.daws88s.online ->
systemctl status
netstat -lntp
ps -ef | grep node
curl http://localhost:8080/health
telnet IP port
frontend.daws88s.online
HTTP status codes
===================
http://daws88s.online/api/transaction
http://daws88s.online/api/transaction
POST
GET
200 OK
100 -> informational
Continuing or switching protocols from HTTPS to HTTP
2XX -> Success
200 -> OK
201 -> Created
204 -> Deleted
3XX -> redirectional
301 -> URL redirection perm
302 -> temp redirection
304 -> Cache
4XX -> Client side error
404 -> Not found
400 -> Bad request, invalid JSON
401 -> Unauthorised, no authentication
403 -> Forbidden, no permission to this
https://emacet.ap.gov.in/api/results/2026/1234567
https://emacet.ap.gov.in/api/results/2026/ -> GOV admins
{
"amountt": 200,
"description": ""
}
5XX -> Server side error
500 -> Internal server error
503 -> Service unavailable
Linkedin Blog
===============
Images
crispy text
Types of DNS records
=====================
NS -> Nameservers, who is managing the domain
SOA -> Start of authority
A -> IPv4
AAAA -> IPv6
MX -> Mail records
TXT -> Verification
CNAME -> Canonical name, another domain
give free for public
paid for business
SQL
======
MySQL
Oracle
Postgress
MSSQL
Schema -> Tables -> Rows and Columns
SQL is not good for huge amount of data
NoSQL
======
MongoDB
data is in documents
{
"name": "mouse",
"vendor": "amazon"
}
{
"name": "mouse",
"vendor": "amazon",
"faq": ""
}
proper data structure -> SQL
un proper data structure, huge data -> NoSQL
Redis
======
Caching Database, key value pair data
Backend -> Database
1. Connecting establish -> Open
2. Request and response
3. Connection close
Backend -> Cache(If not exist) -> Connects to DB -> Keep it inside Cache
TTL -> get response
Queue
======
http -> wait for 30 sec, if server is not responding then error
synchronus
joindevops -> ramesh
asynchronus
order place -> delivery details