Question 1

How to set up a multi-level cache with Carlos?

Accepted Answer

Use the .compose() method to chain levels, like MemoryCacheLevel().compose(DiskCacheLevel()).compose(NetworkFetcher()), creating a pipeline that falls back from memory to disk to network, as shown in the usage examples.

Question 2

Carlos vs Kingfisher: which is better for image caching?

Accepted Answer

Kingfisher is specialized for image downloading and caching with built-in features like placeholders, while Carlos is a general-purpose, composable system; choose Kingfisher for straightforward image needs, Carlos for complex, type-safe cache pipelines.

Question 3

Does Carlos support background fetching or offline storage?

Accepted Answer

Carlos supports disk caching via DiskCacheLevel for offline storage, but background fetching requires integration with iOS background tasks, as the library focuses on cache composition rather than system-level features.

Question 4

How to handle errors in Carlos cache operations?

Accepted Answer

Errors are propagated through Combine publishers, allowing you to use .sink with receiveCompletion to handle failures, such as disk write errors or transformation failures, as demonstrated in the creating requests section.

Question 5

Can I use Carlos with SwiftUI or only UIKit?

Accepted Answer

Carlos is framework-agnostic and uses Combine, so it works with both SwiftUI and UIKit, though you'll need to adapt its asynchronous publishers to SwiftUI's data flow, such as using @Published or ObservableObject.

Question 6

What are the performance costs of using request pooling?

Accepted Answer

Request pooling improves performance by reducing duplicate operations, but it adds overhead for key hashing and management; the benefit outweighs the cost for expensive fetches, but it might be unnecessary for fast cache levels.

Carlos

What is Carlos?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions