How do I set up Porter to import data from an API in PHP?

Create a Porter instance with a PSR-11 container, register a provider like the European Central Bank provider, and use the import method with an Import specification. Quick start guides are available for vanilla PHP and Symfony in the README.

Porter vs Guzzle: which should I use for HTTP requests in PHP?

Porter is designed for durable, asynchronous data imports with testable abstractions and memory efficiency, while Guzzle is a general HTTP client. Choose Porter if you need automatic retries, async concurrency, and SDK-like structures; Guzzle for simpler, synchronous HTTP tasks.

Does Porter support asynchronous imports in PHP 7?

Porter supports async in PHP 7 using coroutines, but the README warns of potential bugs, segfaults, and debugging difficulties. It strongly recommends upgrading to PHP 8.1 for fibers-based async to avoid these issues.

How to handle rate limiting with Porter async imports?

Use the DualThrottle class in the import specification to set limits on connections per second and concurrent connections, preventing service overload. This is detailed in the throttling section of the README.

Can Porter cache API responses to reduce repeated calls?

Yes, Porter supports PSR-6 caching at the connector level. Enable caching via Import::enableCache() and use a CachingConnector wrapper to cache raw responses based on data source hashes, as explained in the caching section.

What providers are available for Porter to use out of the box?

Providers like European Central Bank for forex rates and Steam for gaming data are available. Check the Porter network links in the README for more providers, transformers, and connectors in the ecosystem.

Porter — Durable PHP Data Importer

What is Porter?

Porter is a PHP library for durable and asynchronous data imports, designed to fetch data from APIs, web scraping, or any external source and serve it as iterable record collections. It solves the problem of consuming data at scale by enabling memory-efficient processing and automatic recovery from network failures. The library provides a clean abstraction through providers, resources, and connectors, making it easy to build testable SDKs.

Target Audience

PHP developers building applications that need to import data from external APIs or web services at scale, especially those requiring robust error handling, asynchronous operations, and memory-efficient data processing.

Value Proposition

Developers choose Porter for its combination of durability features, asynchronous capabilities, and memory-efficient design, which together provide a reliable and performant solution for data imports. Its interface triad promotes testability and clean architecture, distinguishing it from simpler HTTP client libraries.

:lipstick: Durable and asynchronous data imports for consuming data at scale and publishing testable SDKs.

Use Cases

Best For

Building PHP SDKs for external APIs with testable abstractions
Importing large datasets from APIs without loading everything into memory
Handling intermittent network failures with automatic retries
Performing concurrent data imports using asynchronous PHP fibers
Applying rate limiting to prevent overwhelming external services
Transforming third-party data with post-import filters and mappers

Not Ideal For

Simple scripts making one-off API calls without need for retry logic or transformations
Applications requiring real-time, continuous data streaming interfaces
Projects stuck on PHP 7.x without plans to upgrade to PHP 8.1+
Microservices where minimizing external dependencies and container overhead is critical

Pros & Cons

Pros

Memory-Efficient Iterators

Processes data as iterable collections, enabling stream-like handling of large datasets without loading everything into memory, as emphasized in the record collections section.

Asynchronous Concurrency

Uses PHP fibers to run multiple imports concurrently, transforming network-bound operations to CPU-bound for optimal performance, with built-in throttling to manage connection rates.

Automatic Retry Logic

Provides durability with configurable retry attempts and exponential backoff for failed fetches, handling intermittent network errors transparently via the ExponentialSleepFetchExceptionHandler.

Testable Interface Triad

Separates providers, resources, and connectors, allowing easy mocking and testing of data import layers, which maps well to API SDK development and is highlighted in the benefits section.

Cons

No Streaming Interface

The README explicitly states a limitation: 'No end-to-end data streaming interface,' restricting use for continuous data flow scenarios.

PHP Version Dependency

Asynchronous features rely on PHP 8.1+ fibers; PHP 7 requires bug-prone coroutines with potential segfaults, making upgrades necessary for stable async performance.

Container Overhead

Requires integration with a PSR-11 compatible container for provider registration, adding setup complexity and dependency management for lightweight applications.

Frequently Asked Questions

What is Porter?

Target Audience

Value Proposition

Use Cases

Best For

Building PHP SDKs for external APIs with testable abstractions
Importing large datasets from APIs without loading everything into memory
Handling intermittent network failures with automatic retries
Performing concurrent data imports using asynchronous PHP fibers
Applying rate limiting to prevent overwhelming external services
Transforming third-party data with post-import filters and mappers

Not Ideal For

Simple scripts making one-off API calls without need for retry logic or transformations
Applications requiring real-time, continuous data streaming interfaces
Projects stuck on PHP 7.x without plans to upgrade to PHP 8.1+
Microservices where minimizing external dependencies and container overhead is critical

Pros & Cons

Pros

Memory-Efficient Iterators

Processes data as iterable collections, enabling stream-like handling of large datasets without loading everything into memory, as emphasized in the record collections section.

Asynchronous Concurrency

Uses PHP fibers to run multiple imports concurrently, transforming network-bound operations to CPU-bound for optimal performance, with built-in throttling to manage connection rates.

Automatic Retry Logic

Provides durability with configurable retry attempts and exponential backoff for failed fetches, handling intermittent network errors transparently via the ExponentialSleepFetchExceptionHandler.

Testable Interface Triad

Separates providers, resources, and connectors, allowing easy mocking and testing of data import layers, which maps well to API SDK development and is highlighted in the benefits section.

Cons

No Streaming Interface

The README explicitly states a limitation: 'No end-to-end data streaming interface,' restricting use for continuous data flow scenarios.

PHP Version Dependency

Asynchronous features rely on PHP 8.1+ fibers; PHP 7 requires bug-prone coroutines with potential segfaults, making upgrades necessary for stable async performance.

Container Overhead

Requires integration with a PSR-11 compatible container for provider registration, adding setup complexity and dependency management for lightweight applications.

Frequently Asked Questions

Porter

What is Porter?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

Porter

What is Porter?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?