search

AxioFramework / axio

Axio Web Framework for Racket
MIT License
20 stars 2 forks source link

Add some suggestions for API design considerations #13

Closed rpless closed 8 years ago

rpless commented 8 years ago

Hi! I've been an on-and-off Racketeer for 6 years now, and as a full-stack web developer, I'm really excited about this project. I wanted to provide some additional suggestions for consideration as this project develops. A lot of these suggestions are based on my experience contributing to and using Finch, and my experience using a number of other web frameworks (specifically Spring, Node/Express, Phoenix, and Spray).

I really like Finch for routing and think it could be good to consider, especially if Typed Racket can be brought in.

I added JOOQ as a suggestion for relational databases, because I like how its API is basically just typesafe SQL. That said, I'm a bigger fan of not forcing a database choice on users, and let them use their own based on their needs.

I've also added some other considerations such as Continuous integration/deployment and open source reporting services (I'm slightly biased here because I'm one of the maintainers of https://github.com/florence/cover and several of its related reporting outputs)

I didn't know where to put this, but one of my real inspirations for building web services has been Marius Erickson's Your server as a function. I think its useful to consider.

I really like the idea of this project and I hope I can be a contributor in the near future.

lojic commented 8 years ago

Thanks Ryan - I'm glad you're excited about the project. I sent you an invite to a Slack channel for the framework. It's just me currently, so no activity, but it will be handy for communication moving forward.