Welcome to hummingbird Discussions!

[adam-fowler]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.
• Please read out Code of conduct before posting here.

Hi,

My name is Adam Fowler and I am the main developer of Hummingbird. I started this project because I wanted to provide an alternative to our big brother Vapor. The project is in its early days at the moment and I would be very interested in hearing feedback. If you would like to contribute to the project, either through issues, conversations here or pull requests that would be even better.

Cheers
Adam

[nonfungibletunji]

Looks clean, just starting looking at the docs. I have been trying to been trying to read from external graphql API service, using a swift server deployed app. working on an example GraphQL server example hummingbird-graphql-kit ????

[adam-fowler]

Unfortunately no hummingbird GraphQL framework available yet. You could look at https://github.com/GraphQLSwift/Graphiti though.

[nonfungibletunji]

That’s the plan S Tunji Turner

…

On Mar 26, 2021, 4:01 PM -0400, Adam Fowler ***@***.***>, wrote: Unfortunately no hummingbird GraphQL framework available yet. You could look at https://github.com/GraphQLSwift/Graphiti though. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[nonfungibletunji]

I read some more of the documentation, what are the differences between this and the Vapor : Server Side Software?

[adam-fowler]

Hi, yes Vapor and Hummingbird do have a number of similarities. A router, middleware are pretty standard across many application frameworks, but the add additional features like extending HBApplication, HBRequest is very similar to Vapor, although done through a slightly different manner, there are similarities elsewhere because I have come from a position of using Vapor and can't avoid being influenced by what has come before.

The main difference between the two is Vapor is a big beast it provides almost everything in one library regardless of whether you need it. The idea behind Hummingbird is to provide only what the user needs. If they don't want TLS don't force them to compile TLS libraries, web sockets, HTTP2 etc.

I split the main code of hummingbird into two repositories so that if someone doesn't like the application framework and only wants the HTTP server they can take the server elements and write their own framework on top.

[nonfungibletunji]

Thanks for the detailed response S Tunji Turner

…

On Mar 31, 2021, 10:27 AM -0400, Adam Fowler ***@***.***>, wrote: Hi, yes Vapor and Hummingbird do have a number of similarities. A router, middleware are pretty standard across many application frameworks, but the add additional features like extending HBApplication, HBRequest is very similar to Vapor, although done through a slightly different manner, there are similarities elsewhere because I have come from a position of using Vapor and can't avoid being influenced by what has come before. The main difference between the two is Vapor is a big beast it provides almost everything in one library regardless of whether you need it. The idea behind Hummingbird is to provide only what the user needs. If they don't want TLS don't force them to compile TLS libraries, web sockets, HTTP2 etc. I split the main code of hummingbird into two repositories so that if someone doesn't like the application framework and only wants the HTTP server they can take the server elements and write their own framework on top. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.