# Data transmission Published articles for Data transmission. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Payment Security Best Practices for SaaS Founders DevFeed: [Payment Security Best Practices for SaaS Founders]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Security](), [Software as a service](), [Encryption](), [tokenization]() Tags: [best-practices](), [checkout](), [collection](), [compliance](), [data-transmission](), [encryption](), [fraud-detection](), [fraud-prevention](), [guide](), [payment](), [payments](), [saas](), [security](), [tokenization]() ### AI overview This guide explains layered payment security practices for SaaS companies, including secure checkout design, HTTPS and TLS, encryption, tokenization, fraud prevention, and incident response. It emphasizes minimizing exposure to card data and using payment-provider infrastructure. ### Source excerpt Essential payment security practices for SaaS companies - from tokenization and 3D Secure to fraud detection and secure checkout design. Protect your customers and revenue. ## JSON - The Fine Print: Part 3 - Zero vs Missing Values DevFeed: [JSON - The Fine Print: Part 3 - Zero vs Missing Values]() Original publisher: [Read original article]() Published: 2025-05-19T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [JSON](), [Go Language](), [Code]() Tags: [api-layers](), [code](), [common-serialization-errors](), [data-serialization](), [data-structure-separation](), [data-transmission](), [data-validation](), [encoding-json](), [go](), [go-json-types](), [go-language-serialization](), [go-language-validation](), [go-type-mapping](), [json](), [json-best-practices](), [json-go-mapping](), [json-marshaling](), [json-unmarshaling](), [json-validation](), [passing-serialized-data](), [rest-apis](), [schema-less-data-format](), [serialization](), [serialization-mistakes](), [serialization-protocols](), [unmarshalling]() ### AI overview This tutorial examines how to distinguish zero values from missing or NULL fields when consuming JSON in Go. It explains basic unmarshalling into structs, notes that absent fields do not cause errors, and introduces DisallowUnknownFields for validating exact JSON input. ### Source excerpt Introduction In part 1 we took a higher level view on serialization in general and JSON in specific. In part 2 we looked at emitting JSON. In part 3, we'll look at an issue you might encounter when consuming JSON, Zero vs NULL field values. To clarify the definition of NULL, this means the absence of value. So here is the question: Given a field in a Go struct set to its zero value, how do you know that zero value was set by the user or it's zero because it was never provided? ## JSON - The Fine Print: Part 2 - Emitting JSON DevFeed: [JSON - The Fine Print: Part 2 - Emitting JSON]() Original publisher: [Read original article]() Published: 2025-02-04T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [JSON](), [API](), [Code](), [Structured-data]() Tags: [api](), [api-layers](), [code](), [common-serialization-errors](), [data](), [data-serialization](), [data-structure-separation](), [data-transmission](), [data-validation](), [encoding](), [encoding-json](), [function](), [go-json-types](), [go-language-serialization](), [go-language-validation](), [go-type-mapping](), [http](), [io](), [io-writer](), [json](), [json-best-practices](), [json-go-mapping](), [json-marshaling](), [json-unmarshaling](), [json-validation](), [map](), [passing-serialized-data](), [properties](), [rest-apis](), [schema](), [schema-less-data-format](), [serialization](), [serialization-mistakes](), [serialization-protocols](), [standard](), [structure](), [writing]() ### AI overview This tutorial explains how to emit JSON in Go using the encoding/json package. It compares json.Marshal, which returns bytes, with json.Encoder, which writes to an io.Writer, and discusses error handling in HTTP handlers. It also demonstrates marshaling maps and structs and using field tags to control JSON property names. ### Source excerpt Introduction In part 1 we took a high-level view on serialization and JSON. In this part, we'll roll our sleeves and start working with JSON, focused on emitting JSON. You might think this is a basic topic, but there is much more to it than just calling json.Marshal. json.Marshal vs json.Encoder The encoding/json package has two main APIs: Marshal and NewEncoder. The Marshal function returns a []byte while the NewEncoder function will write to an io.Writer. The question is: When should you use one API over the other? ## Data transmission reliability over ESP-NOW protocol in indoor environment DevFeed: [Data transmission reliability over ESP-NOW protocol in indoor environment]() Original publisher: [Read original article]() Author: John Lee Published: 2024-12-19T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-NOW](), [Embedded Systems](), [Internet of things](), [Networks](), [Espressif]() Tags: [blog](), [data-transmission](), [embedded-systems](), [esp-now](), [esp32](), [esp32-c6](), [esp32-s3](), [espressif](), [iot](), [low-power](), [networks](), [performance](), [wireless]() ### AI overview This article examines ESP-NOW for reliable, low-power data transmission in indoor IoT and smart applications. It contrasts ESP-NOW with Wi-Fi, describing lower power consumption and lower speed, longer stated range, and compatibility limited to Espressif modules. The supplied text ends before the research evaluation is complete. ### Source excerpt Introduction# Department of Technical Cybernetics at the Faculty of Management Science and Informatics mainly focuses embedded systems and IoT networks, implementing innovative approaches in such systems. Most applications are powered by batteries, and require low power consumption and reliable data transmission. Therefore, the new wireless protocol ESP-NOW has become interesting for implementation in IoT systems. ## Scalable JSON Streaming with HTTP and Go - Ep.5 DevFeed: [Scalable JSON Streaming with HTTP and Go - Ep.5]() Original publisher: [Read original article]() Published: 2024-11-25T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Streaming](), [JSON](), [HTTP](), [Error Handling](), [datasets]() Tags: [chunked-transfer-json](), [code](), [data](), [data-transmission](), [decoding](), [decoding-json-streams](), [efficient-json-handling](), [encoding-json](), [encoding-json-in-go](), [error-handling](), [examples](), [go](), [go-json-encoding](), [go-json-memory-management](), [handling-large-json-files](), [how-to](), [http](), [http-chunked-encoding](), [implementation](), [json](), [json-chunked-transfer](), [json-error-logging](), [json-for-engineers](), [json-lines-format](), [json-lines-ndjson](), [json-streaming](), [json-streaming-in-go](), [memory-efficient-data-transmission](), [memory-efficient-json](), [real-time-data-streaming](), [real-time-json-streaming](), [scalable-json-processing](), [streaming](), [streaming-json-over-http](), [streaming-large-json-datasets]() ### AI overview The final episode of the JSON for Engineers series explains how to stream large JSON datasets efficiently using JSON Lines, Go's encoding/json package, and HTTP/1.1 chunked transfer encoding. It covers incremental encoding and decoding, memory usage, response flushing, and logging errors after streaming begins. ### Source excerpt Introduction: Welcome to the final episode of the JSON for Engineers series! In this concluding session, we tackle the challenges of working with large JSON datasets, exploring efficient strategies for streaming data while minimizing memory usage. These techniques enable developers to handle massive payloads without overburdening system resources, ensuring scalable and cost-effective applications. JSON Streaming: Using JSON Lines for memory-efficient data transmission. HTTP Chunked Encoding: Leveraging HTTP/1.1 chunked transfer encoding for streaming large datasets. Practical Error Handling: Logging and managing errors in streaming JSON responses. This episode starts by addressing the inefficiencies of constructing large JSON objects in memory when working with massive datasets, such as database query results. Instead of consuming significant memory to create one monolithic JSON object, the recommended approach involves using JSON Lines (NDJSON), a format where each line represents a separate JSON object. This method reduces memory requirements by transmitting data incrementally. Using Go's encoding/json package, developers can easily encode and stream multiple JSON objects, as it automatically appends newlines between objects. On the receiving end, decoding JSON streams requires careful looping to handle incoming data dynamically while avoiding memory reuse issues, which could lead to errors or stale data. ## JSON - The Fine Print: Part 1 DevFeed: [JSON - The Fine Print: Part 1]() Original publisher: [Read original article]() Published: 2024-10-23T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [JSON](), [API]() Tags: [api-layers](), [apis](), [common-serialization-errors](), [data-serialization](), [data-structure-separation](), [data-transmission](), [data-validation](), [database](), [elasticsearch](), [encoding-json](), [go-json-types](), [go-language-serialization](), [go-language-validation](), [go-type-mapping](), [json](), [json-best-practices](), [json-go-mapping](), [json-marshaling](), [json-unmarshaling](), [json-validation](), [passing-serialized-data](), [rest-apis](), [schema-less-data-format](), [sensitive-data](), [serialization](), [serialization-mistakes](), [serialization-protocols]() ### AI overview This article explains JSON and serialization fundamentals, then examines common mistakes. It recommends serializing data at program boundaries and using separate data structures for API, business, and storage layers to avoid inefficiency, coupling, and accidental exposure of sensitive data. ### Source excerpt Introduction Everybody knows JSON, it's a simple serialization format and the default format for REST APIs. Like many other topics, there are fine points you should know in order to work with JSON more effectively and avoid common mistakes. In this article we'll explore some big picture aspects and some low level details of using JSON. Serialization Before diving into JSON, I'd like to take a look at serialization in general and discuss common mistakes I've seen my customers make. ## Symmetric vs. asymmetric encryption: Practical Python examples DevFeed: [Symmetric vs. asymmetric encryption: Practical Python examples]() Original publisher: [Read original article]() Author: Josh Amata Published: 2024-05-15T05:00:00Z Content type: tutorial Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Encryption](), [Cryptography](), [Python](), [SSL](), [TLS (Transport Layer Security)]() Tags: [application-security](), [awareness](), [best-practices](), [blog](), [code-security](), [contentlab](), [cryptography](), [data-transmission](), [developer](), [encryption](), [examples](), [guide](), [implement](), [open-source-security](), [python](), [security](), [snyk-code](), [snyk-open-source](), [ssl](), [tls]() ### AI overview This tutorial explains symmetric and asymmetric encryption, including how each uses cryptographic keys to protect sensitive data. It provides practical Python examples and discusses applications in secure transmission, storage, messaging, and TLS/SSL handshakes. ### Source excerpt In this guide, we'll discuss symmetric and asymmetric encryption, implement them in Python, and explore their best practices. ## Tweaking TCP for Real-time Applications: Nagle's Algorithm and Delayed Acknowledgment DevFeed: [Tweaking TCP for Real-time Applications: Nagle's Algorithm and Delayed Acknowledgment]() Original publisher: [Read original article]() Author: umer Published: 2017-03-19T00:00:00Z Content type: tutorial Language: en Sources: [Code Ahoy - Articles]() Topics: [TCP/IP](), [real-time](), [Protocol (disambiguation)](), [Algorithm]() Tags: [algorithm](), [data-transmission](), [protocol](), [real-time](), [tcp-ip]() ### AI overview This tutorial explains how TCP buffering techniques affect real-time applications that send small messages. It focuses on Nagle's algorithm, which combines small messages to reduce packet overhead, and introduces TCP delayed acknowledgment. The article notes that Nagle's algorithm can create performance issues for multiplayer gaming servers. ### Source excerpt TCP is a complex protocol. Don't get me wrong. It is a marvelous piece of engineering that gives us the reliable data transmission guarantee that other protocols don't provide. Reliable data transmission between two devices on the internet is no walk in the park and TCP uses a lot of magic under the hood to make things happen. Generally, it does a fine job of abstracting away low level details and its default settings work fine for most general purpose use cases. However, once in a while, things don't go according to plan and we need to pop open the hood and do some tweaking. It is in these situations, that some knowledge of TCP comes in very handy. By default, TCP uses two buffering techniques to optimize and minimize overhead for general purpose applications. However, if you are building applications that require real-time message delivery for small messages (e.g. chat or control messages), you must have some knowledge of these techniques. Nagle's algorithm TCP delayed acknowledgment Let's look at them in more detail. Nagle's Algorithm If there's no congestion, TCP tacks on a header and sends data out as soon as it gets it from the application. If the application is generating a lot of small messages, the headers can add a lot of overhead: TCP/IP headers are 40-byte, so 1-byte of data is sent as 41-byte packet on the network. A computer programmer named John Nagle came up with an algorithm to reduce the overhead by combining many small messages into a single message. Nagle's algorithm, named after its inventor, is a technique to make TCP more efficient by reducing the number of packets that are sent over the network. Here's the pseudo code for the algorithm: if there is new data to send if the window size >= MaximumSegmentSize and available data is >= MaximumSegmentSize send complete MaximumSegmentSize segment now else if there is unconfirmed data still in the pipe enqueue data in the buffer until an acknowledge is received else send data immediately end if end if