Question 1

How do I add authentication to a Smoke Framework service?

Accepted Answer

Smoke Framework doesn't include built-in authentication; you must implement it manually in the application context or by extending the handler selection. Refer to the extensibility points in the README for custom middleware approaches.

Question 2

Smoke Framework vs Vapor: which is better for Swift backends?

Accepted Answer

Smoke Framework is lighter and more focused on testability and performance with SwiftNIO, ideal for custom APIs. Vapor offers more batteries-included features like ORM and templating, better for full-stack applications with quicker setup.

Question 3

Can I use async/await with Smoke Framework?

Accepted Answer

Yes, distributed tracing supports Swift Concurrency (async/await) from Swift 5.7, as noted in the README. However, you need to enable it explicitly and set up an instrumentation backend.

Question 4

How to deploy a Smoke Framework app to AWS?

Accepted Answer

Since it's a Swift package, compile it for Linux and deploy using AWS Lambda or EC2. The framework's Amazon ties simplify AWS integration, but it can run on any Swift-supported platform like Docker containers.

Question 5

What are the performance benchmarks compared to other frameworks?

Accepted Answer

The README doesn't provide benchmarks, but using SwiftNIO suggests high performance for I/O-bound tasks. Community comparisons with frameworks like Vapor or Kitura might be available for specific use cases.

Question 6

How to handle WebSockets in Smoke Framework?

Accepted Answer

WebSockets aren't built-in; you'd need to extend the framework using its extensible architecture, which involves custom protocol support and handler implementation, as hinted in the Extension Points section.

smoke-framework

What is smoke-framework?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions