EP195: Common Network Protocols Every Engineer Should Know
The 5-Step Playbook for Unlocking the Value of AI (Sponsored)
Successful AI transformation starts with deeply understanding your organization’s most critical use cases. This practical guide from You.com walks through a proven framework to identify, prioritize, and document high-value AI opportunities.
In this AI Use Case Discovery Guide, you’ll learn how to:
Map internal workflows and customer journeys to pinpoint where AI can drive measurable ROI
Ask the right questions when it comes to AI use cases
Align cross-functional teams and stakeholders for a unified, scalable approach
This week’s system design refresher:
Common Network Protocols Every Engineer Should Know
🚀 Learn AI in the New Year! Become an AI Engineer | Learn by Doing | Cohort 3
8 Popular Network Protocols
9 best practices for developing microservices
SPONSOR US
Common Network Protocols Every Engineer Should Know
Ever wonder what actually happens when you click "Send" on an email or join a video call? Every click, message, and API call on the internet relies on network protocols. They define how data moves, who can talk, and how securely it all happens.
At the foundation are transport protocols: TCP ensures reliable delivery, UDP prioritizes speed, and QUIC brings both worlds together over UDP.
On top of that, HTTP powers the web, TLS secures it, and DNS translates names into addresses.
Need remote access? That’s SSH. File transfers? SFTP or SMB.
Real-time chat and media? WebSocket, WebRTC, and MQTT keep data flowing live.
For identity and access, OAuth and OpenID handle authorization and authentication.
In the backend, DHCP, NTP, ICMPv6, and LDAP quietly keep everything synchronized, addressed, and discoverable.
From simple emails (SMTP, IMAP) to encrypted VPNs (WireGuard, IPsec), these protocols form the invisible language that keeps the internet connected and secure.
Over to you: If one protocol suddenly stopped working worldwide, which one would break the internet first?
🚀 Learn AI in the New Year! Become an AI Engineer | Learn by Doing | Cohort 3
After the amazing success of Cohorts 1 and 2 (with close to 1,000 engineers joining and building real AI skills), I’m excited to announce the launch of Cohort 3 of Become an AI Engineer!
This isn’t just another course on AI tools and frameworks. Our mission is to equip engineers with the solid foundation and complete end-to-end skill set required to excel as AI engineers in today’s fast-moving world.
Here’s what sets this cohort apart:
Learn by doing: Build real-world AI applications hands-on, far beyond just watching videos.
Structured, systematic curriculum: Progress step by step from core fundamentals to advanced concepts in a carefully crafted learning path.
Live feedback and mentorship: Receive direct guidance and reviews from experienced instructors and peers.
Strong community support: Learning solo is tough — learning together with a motivated community makes it enjoyable and effective!
If you missed the previous cohorts and want to 𝐥𝐞𝐚𝐫𝐧 𝐀𝐈 𝐢𝐧 𝐭𝐡𝐞 𝐍𝐞𝐰 𝐘𝐞𝐚𝐫, this is your perfect opportunity to join Cohort 3 and level up your AI engineering career.
8 Popular Network Protocols
Network protocols are the key to transferring data between two systems in a network.
FTP (File Transfer Protocol)
Uses separate control and data channels to upload and download files between a client and server.TCP (Transmission Control Protocol)
Establishes a reliable connection using a 3-way handshake (SYN, SYN+ACK, ACK) for accurate data delivery.UDP (User Datagram Protocol)
Sends lightweight, connectionless packets (requests and responses) with minimal latency. Ideal for fast transmissions.HTTP (HyperText Transfer Protocol)
Uses TCP to request and receive web resources (HTML, images) through HTTP requests and responses.HTTP/3 (QUIC)
Built on top of UDP, it enables faster and more reliable connections by multiplexing data streams and reducing latency.HTTPS (Secure HTTP)
Secures HTTP with encryption using public and session keys over a TCP connection, thereby protecting web data.SMTP (Simple Mail Transfer Protocol)
Transfer emails from a sender to a recipient through an SMTP server. It is commonly used for email delivery.WebSocket
Upgrades an HTTP connection to a full-duplex channel for real-time, bidirectional communication like live chats.
A picture is worth a thousand words: 9 best practices for developing microservices
When we develop microservices, we need to follow the following best practices:
Use separate data storage for each microservice
Keep code at a similar level of maturity
Separate build for each microservice
Assign each microservice with a single responsibility
Deploy into containers
Design stateless services
Adopt domain-driven design
Design micro frontend
Orchestrating microservices
SPONSOR US
Get your product in front of more than 1,000,000 tech professionals.
Our newsletter puts your products and services directly in front of an audience that matters - hundreds of thousands of engineering leaders and senior engineers - who have influence over significant tech decisions and big purchases.
Space Fills Up Fast - Reserve Today
Ad spots typically sell out about 4 weeks in advance. To ensure your ad reaches this influential audience, reserve your space now by emailing sponsorship@bytebytego.com.
Many thanks for the great insights!