- 3 minutes to read

Custom Logging, FAQ, Troubleshooting, Intermediate Storage, Asynchronous Logging Custom Logging, intermediate storage, Log API, asynchronous, queue, file share, reliability Should you use intermediate storage or call Log API directly? Learn why asynchronous logging is recommended for reliability.

Intermediate Storage vs Direct Log API Calls

Do I need intermediate storage or can I call Log API directly?

Use intermediate storage for production deployments—asynchronous logging via Pickup Service provides reliability, scalability, and decoupling. Direct Log API calls are not recommended except for simple testing.

Why Intermediate Storage (Asynchronous Logging)

✅ Reliability

If Nodinite Web Server is temporarily unavailable (maintenance, network issues, restarts), your integrations continue running—logs queue up in intermediate storage, Pickup Service fetches them when Nodinite returns.

Direct API: Integration fails or loses log events if Nodinite is unavailable.

✅ Performance

Writing to intermediate storage (Azure Service Bus queue, file share, database) is fast and non-blocking—your integration continues processing without waiting for Nodinite HTTP responses.

Direct API: Every log call waits for HTTP response—adds latency to integration processing (50-200ms per log event).

✅ Scalability

Pickup Service handles burst traffic—1,000 integrations can write 500K logs/day to intermediate storage, Pickup Service ingests at controlled rate without overloading Nodinite.

Direct API: High-volume logging can overwhelm Nodinite Web API with simultaneous connections.

✅ Decoupling

Your integrations don't need network connectivity to Nodinite Web Server—just write to local file share, queue, or database. Pickup Service (running on Nodinite server or nearby) fetches logs asynchronously.

Direct API: Every integration server needs firewall rules, authentication, and network access to Nodinite.

Supported Intermediate Storage Options

Pickup Service fetches logs from:

  • Azure Service Bus Queues - Cloud-native, highly available
  • Azure Storage Queues - Simple, cost-effective
  • File Shares - SMB/CIFS network shares, local folders
  • Databases - SQL Server, PostgreSQL, MySQL tables
  • MSMQ - Windows Message Queuing (legacy)
  • RabbitMQ - Open-source message broker
  • Amazon SQS - AWS queue service

Recommended: Azure Service Bus for cloud deployments, file shares for on-premises simplicity.

When Direct Log API Calls Are Acceptable

Use direct Log API calls only for:

  • Development/testing - Quick prototyping, proof-of-concept
  • Low-volume scenarios - <100 log events/day, non-critical logging
  • Synchronous requirements - Must confirm Nodinite received log before continuing (rare)

Not recommended for production due to reliability and performance trade-offs.

Asynchronous Logging Architecture

graph LR subgraph "Your Integration" A[Integration Logic] --> B[Write JSON Log Event] B --> C[Intermediate Storage] end subgraph "Nodinite Server" D[Pickup Service] --> E[Log API] C --> D end
  1. Integration writes JSON Log Event to intermediate storage (fast, reliable)
  2. Pickup Service asynchronously fetches logs (decoupled, scalable)
  3. Log API ingests into Nodinite (controlled rate, no integration impact)

Read more: Asynchronous Logging architecture and benefits.

Related Topics:
Pickup Service Overview
Asynchronous Logging
JSON Log Event Format

See all FAQs: Troubleshooting Overview

Next Step

Back to Custom Logging Overview