You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iggy.apache.org by "kparisa (via GitHub)" <gi...@apache.org> on 2026/08/31 07:35:11 UTC

[I] feat(sdks): Add Swift SDK for Apache Iggy [iggy]

kparisa opened a new issue, #4001:
URL: https://github.com/apache/iggy/issues/4001

   ### Description
   
   Build and maintain an official Swift SDK for Apache Iggy, providing an idiomatic Swift API for producing and consuming messages and managing Iggy resources.
   
   The SDK should follow the capabilities and conventions of the existing Iggy SDKs while embracing modern Swift features such as structured concurrency, async/await, strong typing, and Swift Package Manager.
   
   The implementation should include the SDK itself, automated tests, examples, CI integration, package distribution, and complete documentation on the Apache Iggy website.
   
   Motivation
   ----
   
   Apache Iggy aims to provide a strong developer experience across programming languages and application environments.
   
   Today, Iggy provides SDKs for Rust, Python, Java, Go, Node.js, C#, C++, and PHP. Adding Swift would expand Iggy’s ecosystem into an important developer community that is currently underserved by streaming infrastructure libraries.
   
   Swift has also evolved beyond application development into a general-purpose language increasingly suitable for:
   
   * server-side applications and services;
   * distributed systems;
   * high-performance networking;
   * systems programming;
   * edge applications;
   * real-time applications;
   * applications spanning clients, edge infrastructure, and backend services.
   
   A native Swift SDK would allow Swift developers to interact directly with Iggy without introducing Java, JVM, or other language/runtime dependencies into their applications.
   
   There is also a particularly natural architectural fit between Swift and Iggy. Both ecosystems emphasize performance, memory safety, predictable resource usage, concurrency, and modern developer ergonomics.
   
   The SDK could make Iggy especially useful for Swift applications that need durable, real-time event streams between devices, services, and backend infrastructure.
   
   Examples include:
   
   * application telemetry and event ingestion;
   * real-time application state and event synchronization;
   * backend services written in Swift;
   * edge-to-cloud streaming;
   * observability pipelines;
   * AI/ML event and inference pipelines;
   * durable event streams for agents and other asynchronous applications.
   
   Most importantly, Swift support strengthens Iggy’s goal of making high-performance streaming infrastructure accessible through the language and development environment that developers already use.
   
   ### Affected area / component
   
   _No response_
   
   ### Proposed solution
   
   Developer experience
   -----
   The Swift SDK should follow established Swift conventions wherever possible.
   
   In particular:
   
   * Swift Package Manager should be the primary package mechanism;
   * public APIs should use idiomatic Swift naming;
   * asynchronous network operations should use async/await;
   * APIs should be strongly typed rather than relying heavily on strings;
   * errors should map into meaningful Swift error types;
   * resource ownership and connection lifecycle should be explicit;
   * documentation should work well with Swift tooling;
   * the SDK should minimize external runtime dependencies.
   
   Transport
   -----
   The first implementation should prioritize a reliable native transport and clean architecture over supporting every Iggy transport immediately.
   
   Phase 1
   
   Implement:
   
   * TCP
   * TLS
   
   using the Iggy binary protocol.
   
   The transport abstraction should be designed so additional transports can be introduced without changing the public client API.
   
   Future
   
   Evaluate support for:
   
   * QUIC
   * HTTP
   * WebSocket
   
   The long-term goal should be alignment with Iggy’s multi-protocol developer experience.
   
   ### Alternatives considered
   
   _No response_
   
   ### Contribution
   
   - [ ] I'm willing to submit a pull request to implement this feature
   
   ### Good first issue
   
   - [ ] I think this could be a good first issue for a new contributor


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Add Swift SDK for Apache Iggy [iggy]

Posted by "javimosch (via GitHub)" <gi...@apache.org>.
javimosch commented on issue #4001:
URL: https://github.com/apache/iggy/issues/4001#issuecomment-5714909306

   Adding a Swift SDK to round out the existing language coverage makes sense for reaching iOS/macOS and server-side Swift developers. The async/await + structured concurrency fit maps cleanly onto Iggy's streaming model, though the TCP binary protocol will need careful bridging into Swift's concurrency primitives to avoid hidden hops.
   One thing worth deciding early: should the SDK target a pure Swift NIO networking layer, or wrap the existing C/C++ SDK via Swift's C interop to reuse the battle-tested protocol implementation? That choice shapes maintenance burden and platform reach (Linux server vs Apple platforms) significantly.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Add Swift SDK for Apache Iggy [iggy]

Posted by "hubcio (via GitHub)" <gi...@apache.org>.
hubcio commented on issue #4001:
URL: https://github.com/apache/iggy/issues/4001#issuecomment-5477094615

   to be decided: bindings approach (like PHP, python and C++) or swift-native implementation.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] feat(sdks): Add Swift SDK for Apache Iggy [iggy]

Posted by "kparisa (via GitHub)" <gi...@apache.org>.
kparisa commented on issue #4001:
URL: https://github.com/apache/iggy/issues/4001#issuecomment-5475291491

   The same package can be contributed to https://github.com/swift-server/ similar to https://github.com/swift-server/swift-kafka-client
   At the least, we can contribute to the swift-server documentation pointing to Iggy's native Swift SDK like many others.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Add Swift SDK for Apache Iggy [iggy]

Posted by "kparisa (via GitHub)" <gi...@apache.org>.
kparisa commented on issue #4001:
URL: https://github.com/apache/iggy/issues/4001#issuecomment-5524537443

   My vote is for Swift native SDK instead of bindings, it's more resource efficient. With our growing community I'm confident that we will be able to maintain the parity with Rust SDK.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Add Swift SDK for Apache Iggy [iggy]

Posted by "RustToMetal (via GitHub)" <gi...@apache.org>.
RustToMetal commented on issue #4001:
URL: https://github.com/apache/iggy/issues/4001#issuecomment-5521320016

   Hi, I'd like to take this issue up.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Add Swift SDK for Apache Iggy [iggy]

Posted by "krishvishal (via GitHub)" <gi...@apache.org>.
krishvishal commented on issue #4001:
URL: https://github.com/apache/iggy/issues/4001#issuecomment-5524433135

   @RustToMetal  I noticed you joined GitHub today. This feature is quite huge and requires experience, do you have LinkedIn or other GitHub account that can prove your Rust/Swift experience? we'd rather not assign this feature to non-experienced devs.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Add Swift SDK for Apache Iggy [iggy]

Posted by "hubcio (via GitHub)" <gi...@apache.org>.
hubcio commented on issue #4001:
URL: https://github.com/apache/iggy/issues/4001#issuecomment-5523625160

   AFAIR @atharvalade also wanted to work on it - perhaps you could split work?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Add Swift SDK for Apache Iggy [iggy]

Posted by "hubcio (via GitHub)" <gi...@apache.org>.
hubcio commented on issue #4001:
URL: https://github.com/apache/iggy/issues/4001#issuecomment-5524351287

   TBH regarding approach bindings vs swift-native i'm leaning swift-native, bindings only as a
   bootstrap if we want something usable sooner.
   
   reason: once #3470 / #3948 (deferred poll) lands, an idle consumer is just one blocked
   socket read. native swift expresses that as an `await` on SwiftNIO / Network.framework
   with zero extra threads, so the OS can suspend the process. a rust binding drags its own
   reactor + timer wheel into the app and you have to drive it across lifecycle
   transitions. on end-user devices that is a real energy difference. plus a pure-swift SPM
   package beats shipping an XCFramework per arch.
   
   fair point for the other side: bindings give protocol parity for free, which is why
   python/php/cpp went that way. and `swift-kafka-client` is itself a wrapper - but over
   librdkafka, plain C, no async runtime attached.
   
   @RustToMetal @atharvalade i think it could split cleanly if you both want in:
   (1) binary protocol codec + TCP/TLS transport
   (2) client API surface, tests/examples/CI shared. under `foreign/swift/`.
   
   but i'm not set in stone, maybe free feature parity with bindings approach is the play here...


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org