Data Transfer Protocols

API Protocols Demystified: When to Use What Understanding which API protocol to use and when is crucial for effective system design. Here's a guide to help you navigate these choices: 1. REST (Representational State Transfer)    When to use:    • For public APIs with broad client support    • When you need simple, stateless operations    • For cache-friendly applications 2. GraphQL    When to use:    • When clients need flexible data querying    • To reduce over-fetching and under-fetching of data    • For applications with complex, nested data structures 3. SOAP (Simple Object Access Protocol)    When to use:    • In enterprise environments with strict security requirements    • When you need built-in error handling and retry logic    • For stateful operations 4. gRPC (gRPC Remote Procedure Call)    When to use:    • For high-performance, low-latency microservices    • In polyglot environments (multiple programming languages)    • When you need bi-directional streaming 5. Webhooks    When to use:    • For event-driven architectures    • To receive real-time updates from external services    • When you want to avoid constant polling 6. WebSockets    When to use:    • For real-time, bi-directional communication    • In applications like chat, live updates, or gaming    • When you need to push data from server to client frequently 7. MQTT (Message Queuing Telemetry Transport)    When to use:    • In IoT and machine-to-machine communication    • For unreliable networks or low-bandwidth environments    • When you need a lightweight publish-subscribe model 8. AMQP (Advanced Message Queuing Protocol)    When to use:    • For enterprise messaging systems    • When you need guaranteed message delivery    • In scenarios requiring complex routing and queuing 9. EDA (Event-Driven Architecture)    When to use:    • For building scalable, loosely coupled systems    • When dealing with unpredictable or bursty workloads    • In microservices architectures 10. EDI (Electronic Data Interchange)    When to use:    • For B2B transactions in industries like retail or healthcare    • When exchanging standardized business documents    • In supply chain management and logistics 11. SSE (Server-Sent Events)    When to use:    • For one-way real-time updates from server to client    • In scenarios not requiring bi-directional communication    • As a simpler alternative to WebSockets for server push Pro Tip: Often, modern applications use a combination of these protocols. The key is to choose the right tool for each specific interaction within your system. GIF Credit - Ivan Novikov

Spent years in embedded systems before I realized most engineers only know 5-6 protocols deeply. The rest? Vague awareness at best. So here's a reference I wish I had earlier — 80+ protocols, one chart. Serial: UART is your bread and butter async link. SPI when you need speed. I2C when you need multiple devices on two wires. I2S for audio. RS-485 when you're dealing with noise and distance. Wireless: BLE for battery-powered devices. Zigbee and Z-Wave for home automation meshes. LoRa when your node is a kilometer away. NFC for tap-to-transfer. UWB for centimeter-accurate positioning. Networking/IoT: MQTT is the go-to for constrained devices talking to a broker. CoAP if you're on UDP. OPC-UA if you're bridging IT and OT. Automotive: CAN is in almost every car made in the last 30 years. LIN for simpler subsystems. FlexRay where safety is non-negotiable. DoIP for diagnostics over Ethernet. Industrial: Modbus is old but still everywhere. EtherCAT for real-time motion. PROFINET for Siemens-heavy factories. HART for analog loops that also need digital data. Aerospace: MIL-1553 has been flying since the 70s and is still going. ARINC 429 in most commercial jets. SpaceWire on satellites. Medical: HL7 moves patient records. DICOM carries your MRI. IEEE 11073 connects personal health devices. Storage: PCIe is the backbone. NVMe is why your SSD is fast. eMMC in your microcontroller. UFS in your phone. Every protocol on this list exists because someone had a real constraint — power, distance, latency, safety, noise. That's the part no datasheet tells you. Save this if it's useful. #EmbeddedSystems #Firmware #IoT #Protocols #Electronics #Engineering #Automotive #Industrial #Aerospace

TCP and UDP are the most basic network protocols every software engineer learns in school but are also the most misunderstood. In this post, I’ll break down the truth about these protocols and debunk some myths that even seasoned developers get wrong. ►Comparing TCP and UDP Across 4 Dimensions 1. Connection-Oriented vs. Not Connection-Oriented      - TCP: Establishes a connection with a handshake before data transfer (e.g., "Hi, can we talk?" → "Yes, let's talk"). There’s a clear start and end to communication.     - UDP: No formal connection setup. It sends data without checking if the receiver is ready or even exists (like sending a message in a bottle).  2. Reliable vs. Unreliable      - TCP: Ensures reliable delivery using acknowledgments and retransmissions. Packets arrive in the correct order.     - UDP: Doesn't confirm delivery or guarantee order. However, “unreliable” is misleading—UDP works well in scenarios where speed is crucial, like video streaming.  3. Flow Control vs. No Flow Control      - TCP: Adjusts its transmission rate based on network conditions, avoiding overwhelming the receiver.     - UDP: Sends data as fast as possible, regardless of the receiver's ability to handle it, which can lead to packet loss.  4. More Overhead vs. Less Overhead      - TCP: Adds headers for features like reliability and flow control, making it bulkier.     - UDP: Minimal headers (source port, destination port, length, checksum) make it lightweight and faster for small data packets. ►Common Myths About TCP and UDP 1. Myth: UDP is Faster      - Reality: Speed depends on the network and data size, not the protocol. UDP has less overhead, which can reduce delays, but transmission speed is identical for both.  2. Myth: TCP is More Secure      - Reality: Neither protocol is inherently secure. Security comes from higher layers, like SSL/TLS, which can work with both.  3. Myth: UDP is Unreliable      - Reality: UDP doesn’t provide reliability at the protocol level, but applications can implement their own checks. Many high-performance systems rely on UDP for its speed.  4. Myth: TCP Guarantees Delivery      - Reality: TCP only informs you whether data was delivered or not. It can’t guarantee delivery if the network itself fails. ► Where to Use TCP and UDP - TCP: Ideal for applications requiring accuracy, like file transfers (HTTP, HTTPS, FTP).   - UDP: Perfect for scenarios where speed matters more than reliability, like video streaming, gaming, or DNS lookups. The takeaway? Both TCP and UDP are critical tools for different jobs. Understanding their strengths and trade-offs is what makes you a better engineer.  What myths have you encountered about TCP and UDP?

𝗜𝗖𝗦 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀: 𝗧𝗵𝗲 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 𝗼𝗳 𝗢𝗧 𝗡𝗲𝘁𝘄𝗼𝗿𝗸𝘀 Every OT environment speaks in protocols. Some are used to control field devices. Some move data to historians. Some support engineering workstations. Some are ordinary IT protocols quietly running inside critical infrastructure. And that is why protocol visibility matters. In an ICS/OT network, you may see: • Modbus TCP on TCP 502 • DNP3 on TCP/UDP 20000 • IEC 60870-5-104 on TCP 2404 • IEC 61850 MMS on TCP 102 • OPC DA using DCOM/RPC and dynamic ports • OPC UA commonly on TCP 4840 • EtherNet/IP on TCP 44818 and UDP 2222 • PROFINET using Ethernet-based real-time communication • BACnet/IP on UDP 47808 • MQTT on TCP 1883 or 8883 with TLS • SNMP on UDP 161/162 • SMB, RDP, DNS, DHCP, NTP, LDAP, Kerberos, SQL, and many more The important point is this: 𝗡𝗼𝘁 𝗲𝘃𝗲𝗿𝘆 𝗽𝗿𝗼𝘁𝗼𝗰𝗼𝗹 𝗶𝗻 𝗢𝗧 𝗶𝘀 𝗮𝗻 𝗢𝗧 𝗽𝗿𝗼𝘁𝗼𝗰𝗼𝗹. Modern OT environments are a mix of: • Control protocols • Vendor protocols • Wireless protocols • Historian/database protocols • Remote access protocols • File transfer protocols • Authentication and directory services • Time synchronization protocols • Discovery and name-resolution protocols For defenders, this creates a simple but powerful question: Do we know which protocols are expected in each OT zone? Because protocol visibility helps answer: • Which assets are actually communicating? • Which protocols are normal for this process area? • Which ports should never appear in Level 2 or Level 3? • Which legacy protocols are still in use? • Which systems are exposing unnecessary services? • Which traffic could support lateral movement? • Which protocols need segmentation, monitoring, or hardening? A protocol cheat sheet is not just a learning document. It becomes a practical OT security tool for: • Asset discovery • Network baselining • Firewall rule review • Threat hunting • Incident response • OT SOC detection engineering • Risk assessment • Segmentation validation In OT cybersecurity, you cannot protect what you do not understand. And you cannot understand the network until you understand the protocols. Know the protocol. Know the asset. Know the risk. #OTSecurity #ICSSecurity #IndustrialCybersecurity #OperationalTechnology #ICS #SCADA #IndustrialAutomation #NetworkSecurity #ThreatHunting #IncidentResponse #CriticalInfrastructure

Top 10 API Protocols Explained Modern applications don’t run as single systems anymore. They operate as connected ecosystems - microservices, cloud platforms, AI agents, mobile apps, and real-time data systems working together. But systems don’t scale because of code alone. They scale because of how systems communicate. That’s where API protocols become critical. This guide breaks down how modern systems exchange data efficiently, reliably, and at scale and why choosing the right protocol directly impacts performance, latency, and architecture design. Inside this guide, you’ll learn: • Why API protocols matter in modern system design • REST - the foundation of most web APIs • GraphQL - flexible data querying for modern apps • Webhooks - event-driven automation without constant polling • SOAP - structured communication for enterprise environments • WebSockets - real-time bidirectional communication • gRPC - high-performance service-to-service communication • MQTT - lightweight messaging for IoT ecosystems • AMQP - reliable enterprise messaging workflows • SSE - simple real-time server-to-client updates • Event-Driven Architecture powering modern data platforms • EDI - standardized business document exchange Key takeaway: There is no “best” protocol - only the right protocol for the problem you’re solving. Modern engineering is no longer just about building applications. It’s about designing how systems talk to each other. If you work in System Design, Data Engineering, Microservices, or AI systems - understanding API protocols is now a fundamental skill. Save this guide for the next time you design an architecture.

I2C, SPI, and UART are commonly used as means for communication between devices within an embedded system due to their simplicity and ease of operation. While they all accomplish a similar goal of sending data, they each have many differences as well as advantages and disadvantages to consider when choosing which to use. I2C, or Inter-Integrated Circuit, is a simple communication protocol often used in embedded systems as a way to transfer data between a master (or multiple masters) and a single slave (or multiple slaves) device. It is a bidirectional two-wire serial bus that uses serial clock (SCL) and serial data (SDA) wires to send and manage data bit by bit between devices connected to the bus. SPI, or Serial Peripheral Interface, is a serial communication protocol often used in embedded systems for high-speed data exchanges between devices on the bus. It operates using a master-slave paradigm that includes at least four signals: a clock (SCLK), a master output/slave input (MOSI), a master input/slave output (MISO), and a slave select (SS) signal. The SCLK, MOSI, and MISO signals are shared by all devices on the bus. The SCLK signal is generated by the master device for synchronization, while the MOSI and MISO lines used for data exchange. Additionally, each slave device added to the bus has its own SS line. The master pulls low on a slave's SS line to select a device for communication. UART, or Universal Asynchronous Receiver/ Transmitter, is a physical circuit in a microcontroller or single integrated circuit (IC) that is used to implement serial communication between devices in an embedded system. Essentially, a UART’s main purpose is to transmit and receive serial data. In UART communication, two UARTs communicate directly with each other; the UART on the sender device, or the transmitting UART, receives parallel data from the CPU (microprocessor or microcontroller) and converts it to serial data. This serial data is transmitted to the UART on the receiver device, or the receiving UART. The receiving UART converts the received serial data back to parallel data and sends it to the CPU. In order for UART to convert serial-to-parallel and parallel-to-serial data, shift registers on the transmitting and receiving UART are used. Unlike communication protocols like I2C and SPI, UART is a physical circuit. While SPI and I2C use a master/slave paradigm to control devices and send data, UART communication incorporates two UART devices to send and receive the data. It also doesn’t operate using a clock so it is necessary for the baud rates of each UART to be within 10% of each other to prevent data loss. While different in these aspects, UART is similar to I2C and SPI certain ways. For instance, both I2C and UART implement a two-wire interface to send and receive data and is often ideal for low-speed data transmission.

Understanding the Three Major Communication Protocols in Embedded & Industrial Systems: UART, I²C, and SPI In modern embedded and industrial applications, microcontrollers and sensors must communicate reliably and efficiently. Three of the most widely used protocols for device-to-device communication are UART, I²C and SPI. Each protocol has its own structure, advantages, and ideal use cases. 1. UART (Universal Asynchronous Receiver/Transmitter) UART is one of the simplest and oldest serial communication methods. How it works: * Communication happens asynchronously no shared clock line. * Data is sent in packets (start bit, data bits, parity, stop bit). * Commonly used for point-to-point links (one transmitter to one receiver). Where it’s used:m * Debugging interfaces * GPS modules * GSM modules (SIM800L) * Communication between two devices Pros: * Very easy to implement * Requires only 2 wires(TX, RX) * Good for long-distance communication Cons: * Not suitable for multiple devices on the same bus * Slower compared to SPI 2. I²C (Inter-Integrated Circuit) I²C is a powerful protocol designed for communication between multiple chips on the same board. How it works: * Uses only 2 wires: SDA (data) and SCL (clock) * Supports multiple masters and multiple slave devices * Each device has a unique 7-bit or 10-bit address Where it’s used: * Sensors like MPU6050, BME280 * OLED displays * RTC modules * Low-speed peripherals inside PCBs Pros: * Multi-device support on a single bus * Very wiring-efficient (just 2 lines) * Good balance of speed and complexity Cons: * Slower than SPI * Requires pull-up resistors * More sensitive to noise in longer cables . SPI (Serial Peripheral Interface) SPI is designed for high-speed, full-duplex data transfer. How it works: * Uses 4 main wires: MISO, MOSI, SCK, SS * Master generates the clock * Very fast and stable for real-time data Where it’s used: * High-speed sensors * SD cards * Flash memory * TFT LCD displays Pros: * Very high data rate * Full-duplex communication * Simple and predictable data timing Cons: * More wires required * Not ideal for many devices unless multiplexed

🌐 Demystifying Network Protocols: A Quick Guide! 📊 Network protocols function as the main pillars that enable communication between devices over a network. Understanding major networking protocols is important for IT professionals. However, there are a lot to remember, in this piece we'll break down some of the most important ones. 🔌 TCP/IP (Transmission Control Protocol/Internet Protocol) This protocol is the underlying method of how information is passed between devices on the internet. While IP is responsible for addressing and routing data packets, TCP takes care of assembling the data into packets, as well as reliable delivery. 🌐 HTTP (Hypertext Transfer Protocol) When accessing websites, HTTP plays a crucial role. It's responsible for fetching and delivering web content from servers to end-users. 🔐 HTTPS (Hypertext Transfer Protocol Secure) An enhanced version of HTTP, HTTPS integrates security protocols (namely TLS) to encrypt data, ensuring a secure and confidential exchange between browsers and websites. 📂 FTP (File Transfer Protocol) As the name suggests, FTP is used for transferring files (uploading and downloading) between computers on a network. 📧 UDP (User Datagram Protocol) A more streamlined counterpart to TCP, UDP transmits data without the overhead of establishing a connection, leading to faster transmission but without the guarantee that the data will be delivered or in order. 📬 SMTP (Simple Mail Transfer Protocol) The driving force behind email communication, SMTP manages the formatting, routing, and delivery of emails between mail servers. 🔒 SSH (Secure Shell) Secure Shell is a cryptographic network protocol that ensures safe data transmission over an unsecured network. It provides a safe channel, making sure that hackers can't interpret the information by eavesdropping. 🚀 Understanding these protocols is crucial for anyone in the IT and networking field. They are the building blocks of the internet and digital communication. 💬 I'd love to hear your thoughts. Are there any other protocols or concepts you'd like to add to this list?

🌐 Common Network Protocols — The Backbone of Modern Communication Every click, email, or video stream relies on network protocols that define how data is transmitted, secured, and managed. Here’s a breakdown of the most essential ones every network or telecom engineer should know 👇 🔒 1. HTTPS (Hypertext Transfer Protocol Secure) Layer: Application Port: 443 What: Enables secure web communication between browsers and servers. Why: Encrypts data using SSL/TLS to protect sensitive information like passwords and payment details. ➡️Example: Accessing secure websites (https://www.example.com). 📂 2. FTP (File Transfer Protocol) Layer: Application Ports: 20 (Data), 21 (Control) What: Transfers files between systems. Why: Efficient for uploading/downloading large files over a network. ➡️Example: Moving website files to a hosting server. 💻 3. Telnet Layer: Application Port: 23 What: Provides command-line access to remote devices. Why: Used for network administration (though now mostly replaced by SSH). 🌍 4. DNS (Domain Name System) Layer: Application Port: 53 What: Converts domain names into IP addresses. Why: Simplifies web navigation by allowing access through names instead of numbers. ➡️Example: Resolving www.google.com → 142.250.190.14. 🧠 5. DHCP (Dynamic Host Configuration Protocol) Layer: Application Ports: 67 (Server), 68 (Client) What: Automatically assigns IP addresses and configurations. Why: Simplifies network setup and ensures smooth connectivity. 📧 6. SMTP (Simple Mail Transfer Protocol) Layer: Application Port: 25 / 587 What: Sends emails between mail servers. Why: Ensures messages reach the right recipient reliably. 📬 7. POP3 (Post Office Protocol v3) Layer: Application Port: 110 / 995 (Secure) What: Downloads emails to local clients. Why: Allows offline email access and saves server space. 📥 8. IMAP (Internet Message Access Protocol) Layer: Application Port: 143 / 993 (Secure) What: Lets users access emails directly from the server across multiple devices. Why: Keeps emails synced on all platforms for better management. ⚙️ 9. TCP (Transmission Control Protocol) Layer: Transport What: Provides reliable, ordered data delivery using a 3-way handshake (SYN, SYN-ACK, ACK). Why: Ensures no packet loss and maintains data integrity. Example: Used in HTTPS, FTP, and SMTP. ⚡ 10. UDP (User Datagram Protocol) Layer: Transport What: Sends data quickly without reliability checks. Why: Prioritizes speed over accuracy—ideal for streaming, VoIP, and gaming. These protocols form the core of all communication networks — ensuring security, reliability, and speed across devices and systems. Understanding them is key for any Network Engineer, Cloud Specialist, or Telecom Professional. 🚀 #Networking #Telecom #5G #CloudNetworking #NetworkEngineer #Cybersecurity #Protocols #DNS #TCPIP #Learning #Technology #TelecomCommunity

Think network ports and protocols are just IT problems? Think again. They're everywhere in OT/ICS as well! -> HMIs with web interfaces -> Historians storing lots and lots of data -> PLCs running unauthenticated protocols -> Engineering workstations with remote access -> Network devices with exposed admin interfaces You'll see many protocols unique to OT. You'll also see many IT protocols in OT networks too! Surprise! Here's a list of some you should be familiar with: 1. TCP 22 (SSH) Used for administrative access via the command line over an encrypted channel 2. TCP 80 (HTTP) Used to access web interfaces on different assets such as SCADA, HMIs, PLCs and firewalls 3. TCP 102 (S7) Siemen’s proprietary OT/ICs protocol; often seen in power plants, refineries and many more 4. UDP 161 (SNMP) Just like in IT, Simple Network Management Protocols is used to query data about an asset 5. TCP 443 (HTTPS) Encrypted version of HTTP used o access web interfaces on different assets in OT network 6. TCP 502 (Modbus) The most commonly used (unauthenticated) protocol in OT/ICS; you can find it EVERYWHERE 7. TCP 1433 (MS SQL) Microsoft’s SQL Server has served as the backbone of storing historical data for decades 8. TCP 1883 (MQTT) The unencrypted version for M2M (machine-to-machine) comms; encrypted runs on TCP 8883 9. TCP 3389 (MS RDP) Microsoft’s Remote Desktop Protocol used to remotely login to Windows assets for work 10. TCP 4840 (OPC UA) Acts as a universal translator and coordinator between systems made by different vendors 11. TCP 20000 (DNP3) OT/ICS protocol used in SCADA for managing remote assets (RTUs, IEDs, etc) over a WAN link 12. TCP 34964 (Profinet) Another protocol running over Ethernet for time-sensitive communication in OT/ICS 13. TCP 44818 (EtherNet/IP) Based on Common Industrial Protocol (CIP), common to see in AB/Rockwell Automation. 14. UDP 47808 (BACnet) Designed for buiding automation controls from HVAC & lightning to access controls. P.S. Don't forget - you can run any service or protocol on any port! But these are some of the default ports to be aware of. And to secure! P.P.S. What would you add? 🔔 Follow Mike Holcomb for more OT/ICS cybersecurity ♻️ Useful? Share to help others! 📩 Join 5,900+ others on my newsletter - https://lnkd.in/ePTx-Rfw 📽️ FREE videos for learning OT/ICS cyber - https://lnkd.in/eif9fkVg