search

Christop406 / time_library

A new way to view any history
0 stars 0 forks source link

Decide on a backend stack #2

Open Christop406 opened 5 years ago

Christop406 commented 5 years ago

We need to decide how the software is going to run on the backend. A node backend seems fitting, but what library should we use to serve content? Express? We can discuss on this issue

MarkoVlaic commented 5 years ago

Although express is something everyone is familiar with I would like to propose koa. It's built by the team behind express and looks promising. I also think that we should take an opportunity to learn something new while working on this project. I have no experience with koa besides reading the documentation so please do take this with a grain of salt.

Christop406 commented 5 years ago

Koa looks interesting, potentially simpler than express. Does it work well with typescript?

Sent with GitHawk

gentleadam commented 5 years ago

Never used it but looks interesting.

Christop406 commented 5 years ago

We also may want to look into a technology like graphQL instead of a standard REST API, since we will have data that is so embedded into itself

Sent with GitHawk

MarkoVlaic commented 5 years ago

What would we gain by using graphQL?

Christop406 commented 5 years ago

Well, since we’re going to have many types of data that all embed into each other, it might make sense to get the data in that way since we can never be sure of what is going to be returned exactly in one API call. Also, it could be a good learning experience. I am up for doing graphQL later on if it’s too complex for now

Sent with GitHawk

MarkoVlaic commented 5 years ago

I've read up a bit on graphQL and I like the idea of using it. We should maybe start by implementing a basic api without it and add it later on when we feel the need. If you think it's better we start with it from the beggining it's fine by me as long as it doesn't add a lot of complexity.

MarkoVlaic commented 5 years ago

I've also stumbled upon this thread today (https://www.reddit.com/r/node/comments/ckn6do/egg_vs_koa_2019/?utm_medium=android_app&utm_source=share). Do you think egg would make our lives easier?

Christop406 commented 5 years ago

To be honest, egg might be too much for what we need, I'd pick Express over it. Unless you feel confident about using egg, in which case you can start development and submit a PR

MarkoVlaic commented 5 years ago

I'm just bouncing ideas around. I've gone through a couple of egg guides and I see why you think it's too much. Will we stick to using koa then?

Christop406 commented 5 years ago

If you think there is a reason to use koa over express I am fine with koa

Sent with GitHawk

MarkoVlaic commented 5 years ago

I just think it's a learning opportunity and I like it's middleware system plus the async/await syntax. On the other hand more people could contribute if we use express and all of us have more experience with it. We should maybe make a poll on the slack channel?

Christop406 commented 5 years ago

Sure, you can make the poll. I'm fine with either. We can also write our own abstractions over koa to make it more user friendly, if that's a concern

-- Chris Gilardi cgilardi97@gmail.com (650) 544-9839 On Aug 2, 2019, 8:26 AM -0700, MarkoVlaic notifications@github.com, wrote:

I just think it's a learning opportunity and I like it's middleware system plus the async/await syntax. On the other hand more people could contribute if we use express and all of us have more experience with it. We should maybe make a poll on the slack channel? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.