Mohamed Abukar

𝟲 𝗘𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 𝗔𝗣𝗜 𝗦𝘁𝘆𝗹𝗲𝘀 🔀

An API style is like a secret handshake 🤝 between two computers, helping them share and understand each other's messages. There are various methods of handshakes and each has its own way of sending and receiving information!

Here are the 6 most important API styles you need to know:

1️⃣ SOAP 🧼

An XML-based communication protocol with strict contracts. It's mostly used over HTTP(S) 🌐 and is popular in enterprise environments 🏢.

What Engineers need to know: As a software or DevOps engineer, understanding SOAP is crucial for working in enterprise environments, especially where legacy systems still exist.

2️⃣ REST API 🔄

An easy-to-understand, resource-focused API style. It uses standard HTTP methods 🌐 and often employs JSON for data.

What Engineers need to know: REST APIs are common, so mastery of their design and use is a key skill for developers and DevOps.

3️⃣ gRPC ⚙️

An API style emphasizing remote procedure calls (RPCs). It uses HTTP/2 for transport and Protocol Buffers for data serialization, making it ideal for efficient, low-latency microservices 🔬.

What Engineers need to know: Knowledge of gRPC can help in designing and maintaining high-performing, scalable microservices.

4️⃣ GraphQL 📊

A flexible query language for APIs allowing clients to request specific data. It was developed by Facebook and can combine data from multiple sources 🔄.

What Engineers need to know: Understanding GraphQL can help in creating efficient APIs that prevent over-fetching and under-fetching of data.

5️⃣ Websocket 🔌

A protocol for real-time, bidirectional communication 🔄. It maintains a long-lived connection and is great for web apps needing live updates 📲.

What Engineers need to know: Websockets are essential for applications requiring real-time data exchange, like chat applications or real-time analytics.

6️⃣ Webhook 🎣

A server-side, event-driven mechanism. It sends HTTP callbacks (usually POST requests) when specific events occur, perfect for real-time data updates or third-party service integration 🔗.

What Engineers need to know: Webhooks are crucial for setting up automated workflows and integrations, a common task in DevOps and software development.

To stay ahead of the curve, software and DevOps engineers need to understand these API styles, their benefits, and their use cases. This will allow them to design and implement efficient, scalable, and functional systems. 🚀💻

Image creds: Brij kishore Pandey

Enjoying my content on Software Engineering, DevOps and Systems Design? Follow me here >> Mohamed Abukar 🙏🏽

#softwareengineering #api #architecture

🔹 API Gateway - a nice example.

An API Gateway is a server that acts as an intermediary for API requests, handling tasks such as authentication, rate limiting, and routing requests to appropriate microservices. It allows decoupling of the client from the backend services and facilitates API management.

------------------------------------------------------------
📌 If you like my posts, please follow me here - Mohamed Abukar and hit the 🔔 on my profile to get notifications for all my new posts.

Blog: https://blog.coderco.io/ (More Software Engineering, Systems Design & DevOps articles & blogs)

#systemdesign #softwareengineering #apigateway

𝗪𝗵𝗮𝘁 𝗵𝗮𝗽𝗽𝗲𝗻𝘀 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝘁𝘆𝗽𝗲 𝗮 𝗨𝗥𝗟 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗯𝗿𝗼𝘄𝘀𝗲𝗿?

The process involves fundamental components like browser, your computer’s operating system, your internet service provider (ISP) , the server where you host the site and the services running on that server.

𝟭.𝐘𝐨𝐮 𝐭𝐲𝐩𝐞 𝐡𝐭𝐭𝐩𝐬://𝐰𝐰𝐰.𝐭𝐡𝐞𝐭𝐫𝐚𝐢𝐧𝐥𝐢𝐧𝐞.𝐜𝐨𝐦/𝐦𝐲-𝐭𝐢𝐜𝐤𝐞𝐭𝐬 𝐢𝐧𝐭𝐨 𝐲𝐨𝐮𝐫 𝐛𝐫𝐨𝐰𝐬𝐞𝐫 𝐚𝐧𝐝 𝐞𝐧𝐭𝐞𝐫

Here, HTTPS is a scheme, which tells the browser to make a connection to the server using TLS. www.thetrainline.com is the domain name of the site and it points to a specific IP address of a server. And /my-tickets is a random path to the resource you need.

𝟮. 𝐓𝐡𝐞 𝐛𝐫𝐨𝐰𝐬𝐞𝐫 𝐜𝐡𝐞𝐜𝐤𝐬 𝐭𝐡𝐞 𝐜𝐚𝐜𝐡𝐞 𝐟𝐨𝐫 𝐚 𝐃𝐍𝐒 𝐫𝐞𝐜𝐨𝐫𝐝 𝐭𝐨 𝐟𝐢𝐧𝐝 𝐭𝐡𝐞 𝐜𝐨𝐫𝐫𝐞𝐬𝐩𝐨𝐧𝐝𝐢𝐧𝐠 𝐈𝐏 𝐚𝐝𝐝𝐫𝐞𝐬𝐬 𝐨𝐟 𝐭𝐡𝐞𝐭𝐫𝐚𝐢𝐧𝐥𝐢𝐧𝐞.𝐜𝐨𝐦/𝐦𝐲-𝐭𝐢𝐜𝐤𝐞𝐭𝐬

After you’ve typed the URL into your browser and pressed enter, the browser needs to figure out which server on the Internet to connect to. It looks for the IP address of the server hosting the website using the domain you typed to accomplish that. DNS lookup is done here. Here, it determines whether we can locate it in the cache. If not, DNS searches domain name servers from the root to the third level.

𝟯. 𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝗶𝗻𝗶𝘁𝗶𝗮𝘁𝗲𝘀 𝗧𝗖𝗣 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝘀𝗲𝗿𝘃𝗲𝗿

TCP, is used throughout the public Internet routing to route packets from a client browser request through the router, the ISP, through an internet exchange to switch ISPs or networks, and finally to find the server with the IP address to connect to. This is an inefficient route to take to get there. Instead, a lot of websites utilise a CDN (like AWS CloudFront) to cache both static and dynamic material closer to the browser.

𝟰. 𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝘀𝗲𝗻𝗱𝘀 𝘁𝗵𝗲 𝗛𝗧𝗧𝗣 𝗿𝗲𝗾𝘂𝗲𝘀𝘁 𝘁𝗼 𝘁𝗵𝗲 𝘀𝗲𝗿𝘃𝗲𝗿

Now that the browser is connected to the server, it complies with the HTTP(s) protocol's requirements for communication. To request the contents of the page, the browser first sends an HTTP request to the server. The body, headers and request line of an HTTP request are all there.

𝟱. 𝗦𝗲𝗿𝘃𝗲𝗿 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗿𝗲𝗾𝘂𝗲𝘀𝘁 𝗮𝗻𝗱 𝘀𝗲𝗻𝗱𝘀 𝗯𝗮𝗰𝗸 𝗮 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗲

The server accepts the request and determines how to handle it depending on the data in the request line, headers, and body. The server receives the material at this URL for the GET /page/ HTTP/1.1 requests, builds the response, and then delivers it back to the client with an HTTP status code.

𝟲. 𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝗿𝗲𝗻𝗱𝗲𝗿𝘀 𝘁𝗵𝗲 𝗰𝗼𝗻𝘁𝗲𝗻𝘁

The browser checks the response headers for instructions on how to render the resource after receiving the server's response. The Content-Type header lets the browser know that an HTML resource was received in the response body.

image creds: @manekinekko

#softwareengineering #networking #dns

You can easily get lost with the millions of GitHub repositories out there.

𝐇𝐞𝐫𝐞 𝐚𝐫𝐞 𝐚 𝐜𝐮𝐫𝐚𝐭𝐞𝐝 𝐥𝐢𝐬𝐭 𝐨𝐟 𝐆𝐢𝐭𝐇𝐮𝐛 𝐫𝐞𝐩𝐨𝐬𝐢𝐭𝐨𝐫𝐢𝐞𝐬 𝐭𝐡𝐚𝐭 𝐰𝐢𝐥𝐥 𝐫𝐞𝐚𝐥𝐥𝐲 𝐡𝐞𝐥𝐩 𝐲𝐨𝐮 𝐭𝐨 𝐚𝐝𝐯𝐚𝐧𝐜𝐞 𝐲𝐨𝐮𝐫 𝐜𝐚𝐫𝐞𝐞𝐫 𝐢𝐧 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠, 𝐃𝐞𝐯𝐎𝐩𝐬, 𝐒𝐑𝐄 𝐚𝐧𝐝 𝐦𝐨𝐫𝐞! 📚

1. A list of programming tutorials in which aspiring software engineers learn how to build an application from scratch.

📌  (https://lnkd.in/enxAaRv4)

2. Contains questions and exercises on various technical topics related to DevOps and SRE

📌  (https://lnkd.in/eqR-Y5Pn)

3. Useful resources for Site Reliability Engineering and DevOps

📌  (https://lnkd.in/eRJkKPmE)

4. Learn how to design large-scale systems

📌  (https://lnkd.in/e4q_gmGK)

5. A collections of Linux SysAdmin/DevOps questions to help you getter a better understanding of Linux

📌  (https://lnkd.in/ejnAuQtY)

6. A study guide for Software Engineers looking to get better at Data Structures & Algorithms

📌  (https://lnkd.in/eHfVhAHA)

7. A collection of (mostly) technical things every developer should aim to know

📌 (https://lnkd.in/eYvUChpG)

8. Community driven roadmaps, articles and resources for Devs, Architects, QA and DevOps and more!

📌  (https://lnkd.in/ew87589P)

9. Curated questions and answers to test your knowledge on Linux

📌  (https://lnkd.in/eTjMHBHq)

10. Curated collection of resources for frontend web developers

📌 (https://lnkd.in/ekShjrRQ)

11. Learn Software Architecture, Design patterns, DDD, SOLID principles and good software practices

📌  (https://lnkd.in/eK4vFGf9)

12. A set of guidelines for best practices, styles and methods for various programming languages.

📌  (https://lnkd.in/ewc85mED)

#softwareengineering #coding #systemdesign #devops #sre #github

𝗪𝗵𝗮𝘁 𝗵𝗮𝗽𝗽𝗲𝗻𝘀 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝘁𝘆𝗽𝗲 𝗮 𝗨𝗥𝗟 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗯𝗿𝗼𝘄𝘀𝗲𝗿?

A common interview question I ask to test the depth of knowledge of interviewee.

𝟭. 𝗬𝗼𝘂 𝘁𝘆𝗽𝗲 𝗵𝘁𝘁𝗽𝘀://𝘄𝘄𝘄.𝘁𝗵𝗲𝘁𝗿𝗮𝗶𝗻𝗹𝗶𝗻𝗲.𝗰𝗼𝗺/𝗺𝘆-𝗮𝗰𝗰𝗼𝘂𝗻𝘁/𝗯𝗼𝗼𝗸𝗶𝗻𝗴𝘀 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗯𝗿𝗼𝘄𝘀𝗲𝗿 𝗮𝗻𝗱 𝗲𝗻𝘁𝗲𝗿
Here, HTTPS is a scheme, which tells the browser to make a connection to the server using TLS.
www.thetrainline.com is the domain name of the site and it points to a specific IP address of a server. And /my-tickets is a random path to the resource you need.

𝟮. 𝗧𝗵𝗲 𝗯𝗿𝗼𝘄𝘀𝗲𝗿 𝗰𝗵𝗲𝗰𝗸𝘀 𝘁𝗵𝗲 𝗰𝗮𝗰𝗵𝗲 𝗳𝗼𝗿 𝗮 𝗗𝗡𝗦 𝗿𝗲𝗰𝗼𝗿𝗱 𝘁𝗼 𝗳𝗶𝗻𝗱 𝘁𝗵𝗲 𝗰𝗼𝗿𝗿𝗲𝘀𝗽𝗼𝗻𝗱𝗶𝗻𝗴 𝗜𝗣 𝗮𝗱𝗱𝗿𝗲𝘀𝘀 𝗼𝗳 𝘁𝗵𝗲𝘁𝗿𝗮𝗶𝗻𝗹𝗶𝗻𝗲.𝗰𝗼𝗺/𝗺𝘆-𝗮𝗰𝗰𝗼𝘂𝗻𝘁/𝗯𝗼𝗼𝗸𝗶𝗻𝗴𝘀
After you’ve typed the URL into your browser and pressed enter, the browser needs to figure out which server on the Internet to connect to. It looks for the IP address of the server hosting the website using the domain you typed to accomplish that. DNS lookup is done here. Here, it determines whether we can locate it in the cache. If not, DNS searches domain name servers from the root to the third level.

𝟯. 𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝗶𝗻𝗶𝘁𝗶𝗮𝘁𝗲𝘀 𝗧𝗖𝗣 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝘀𝗲𝗿𝘃𝗲𝗿
TCP, is used throughout the public Internet routing to route packets from a client browser request through the router, the ISP, through an internet exchange to switch ISPs or networks, and finally to find the server with the IP address to connect to. This is an inefficient route to take to get there. Instead, a lot of websites utilise a CDN (like AWS CloudFront) to cache both static and dynamic material closer to the browser.

𝟰. 𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝘀𝗲𝗻𝗱𝘀 𝘁𝗵𝗲 𝗛𝗧𝗧𝗣 𝗿𝗲𝗾𝘂𝗲𝘀𝘁 𝘁𝗼 𝘁𝗵𝗲 𝘀𝗲𝗿𝘃𝗲𝗿
Now that the browser is connected to the server, it complies with the HTTP(s) protocol's requirements for communication. To request the contents of the page, the browser first sends an HTTP request to the server. The body, headers and request line of an HTTP request are all there.

𝟱. 𝗦𝗲𝗿𝘃𝗲𝗿 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗿𝗲𝗾𝘂𝗲𝘀𝘁 𝗮𝗻𝗱 𝘀𝗲𝗻𝗱𝘀 𝗯𝗮𝗰𝗸 𝗮 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗲
The server accepts the request and determines how to handle it depending on the data in the request line, headers, and body. The server receives the material at this URL for the GET /page/ HTTP/1.1 requests, builds the response, and then delivers it back to the client with an HTTP status code.

𝟲. 𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝗿𝗲𝗻𝗱𝗲𝗿𝘀 𝘁𝗵𝗲 𝗰𝗼𝗻𝘁𝗲𝗻𝘁
The browser checks the response headers for instructions on how to render the resource after receiving the server's response. The Content-Type header lets the browser know that an HTML resource was received in the response body.

Image creds: @manekinekko

#softwareengineering #systemsdesign #networking #dns

🌐 HTTP Basics - Foundation of data communication on the web

🔹 Foundation of data communication on the web
🔹Request-response protocol
🔹 Important for Software & DevOps Engineers to understand

📤 HTTP Request Header:

🔹 Sent by the client to the server
🔹 Contains:Request line (method, URL, protocol version)
🔹Header fields (e.g., Host, User-Agent, Accept)

📥 HTTP Response Header:

🔹Sent by the server to the client
🔹Contains:Status line (protocol version, status code, reason phrase)
🔹Header fields (e.g., Content-Type, Content-Length)
🔹Status codes help diagnose and troubleshoot issues

🛠️ Best Practices:

🔹 Use HTTPS for encrypted communication
🔹Handle caching and compression correctly
🔹Configure security-related headers
🔹Manage cookies and sessions securely

📚 In conclusion, understanding HTTP request and response headers is a fundamental skill for Software and DevOps Engineers. Familiarity with the structure, methods, and common header fields, along with best practices for secure and efficient communication, will enable them to build, maintain, and troubleshoot web applications and services effectively.

#softwareengineering #http #web #architecture #data