Nirav pfp
Nirav
@nirav-joshi
During the research on the preliminary software architecture design of our gamification project, I came across many new learnings that I want to share. Client-server architecture is one of these. πŸ‘‡
1 reply
0 recast
0 reaction

Nirav pfp
Nirav
@nirav-joshi
πŸ–₯️ Client: Any entity using a service, typically a computer. πŸ–₯️ Server: Provides services to clients, as well as a computer.
1 reply
0 recast
0 reaction

Nirav pfp
Nirav
@nirav-joshi
π—–π—Ήπ—Άπ—²π—»π˜-π—¦π—²π—Ώπ˜ƒπ—²π—Ώ π—”π—Ώπ—°π—΅π—Άπ˜π—²π—°π˜π˜‚π—Ώπ—² πŸ‘‡
1 reply
0 recast
0 reaction

Nirav pfp
Nirav
@nirav-joshi
- Hosts, manages and delivers resources/services βš™ requested by the client. - Transfers requests ⬆ and services ⬇ through a network. - Divides workload between client and server, which can be on the same system or connected via a network.
1 reply
0 recast
0 reaction

Nirav pfp
Nirav
@nirav-joshi
- Involves multiple devices πŸ“± connected to a central server via the internet or other network. - Client requests data, server processes and sends back data in packets πŸ“¦ . - Client programs run only when needed; server programs run continuously to respond to requests.
1 reply
0 recast
0 reaction

Nirav pfp
Nirav
@nirav-joshi
Understanding this architecture was crucial for my project, as multiple clients/users will be connecting with our service, and one key component called "Authoritative Server" is required, something I will discuss in future posts.
0 reply
0 recast
0 reaction