Hello everyone and welcome.
In this particular video we will learn about client server architecture.
It is one of those fundamental that you need to understand.
MCP relies heavily on the client server architecture.
So it's important for us to learn about client server architecture.
Now if you are already familiar with how client server architecture works, then please feel free to
skip this video and move on to the next one.
If you want to understand and have a refresher on client server architecture, then please stay on this
video and we will cover why client server matters and how it solves the problems that we're connected
to.
AI agents.
Having said that, let's move on to the client server communication.
So there are three main components involved in the client server architecture a client is a typical
application, any computer or device that requests services or resources.
Server is a powerful computer or software that provides services and resources to clients.
And then there is a communication that happens over internet.
This is a standardized protocol that establishes reliable data exchange between client and server components.
So now how the process works.
A client on the left hand side of the image sends a request, such as a web page or access in a database.
Then this request travels over network to reach server.
Then the server processes the request and prepares the requested data for service, and the response
then is sent back to the client.
And then client displays the responses on the web page or uses the response to do further processing.
This is typically how the client work application communicates over internet.
So this is where we have a critical role for established standards like HTTP or FTP provide a critical
role for software development because they establish common protocols that allow different systems to
communicate effectively without standards.
Every system would essentially speak its own language, making integration nearly impossible.
So now let's understand a little bit more about Rest API and the challenges that Lem has using APIs.
So Rest API is essentially representational state transfer, which is a widely used protocol for communicating
using web APIs.
You interact with Rest API daily through social media, messaging apps and mobile applications.
It has a standard in terms of using methods HTTP, post, get, put, delete, and the responses are
also structured in JSON format.
So now why standards matter?
It provides a universal language for systems to communicate.
When companies they follow Rest standards, developers can essentially connect and use their services
with those standards in place.
So this is where the engineering principle relies on establishing standards.
They're essentially what makes complex systems possible.
Without standards, every company would create unique systems, making it nearly impossible to scale
and manage a complex system.
So the problem of right language model connecting with tools is very prominent.
Think of large language model connecting to a tool that speaks different languages English, Spanish,
Japanese.
Every service provides their API contract differently, requiring the information to be set up differently.
The real problem here is that you cannot have APIs or services that gives responses in different formats
and different standards.
It is nearly impossible for law or any technology to scale.
This is where MCP comes to rescue, and it's important how MCP creates standard that Lem can relay on.
And all the underlying services also has to rely on.
And making this scalable, manageable and seamless across the technology that we are evolving into.
Thank you.
I'll see you in the next video.