RestyaPlatform / board

Trello like kanban board. Based on Restya platform.
http://restya.com/board/
Open Software License 3.0
2.05k stars 383 forks source link

Restyaboard v2 - whishlist braindump #1835

Open rrjanbiah opened 6 years ago

rrjanbiah commented 6 years ago

CC @BlackDark

Frontend

  1. React Native that works in web too (or Preact?)
  2. Bootstrap 4 or?
  3. PWA

Backend

  1. GraphQL for query API
  2. CRUD API
  3. 1250

  4. Non-sticky sessions / microservices ?

DevOps

  1. Docker

Note

Feel free to add anything in your mind

BlackDark commented 6 years ago

Frontend

Main point is to decide if you want to build native apps or stay with webapps. If you stick to PWA and support the required caching for offline usage you could avoid implementing native apps.

Backend

DevOps

rrjanbiah commented 6 years ago

Few React Native toolkits that support multiple platforms

rrjanbiah commented 6 years ago

GraphQL really flexible but a little harder to implement and support compared to REST. You can request those informations which you really need.

Then what about gRPC?

Not sure what your ideas are for 4

Basically microservices is about splitting endpoints across different services (advantage: code will be less and can easily scale up and scale down). In that case, session should not be sticky. We may use JWT or signed cookies, instead of sticky session.

itzmeank commented 6 years ago

@rrjanbiah @BlackDark I am not expert on front end, but I think for the back end micro services architecture might be a better approach, and like @rrjanbiah pointed out code will be less and can easily scale up and scale down... so my vote would also be for micro services but better you all discuss and make it better :)

praveenscience commented 6 years ago

I would kinda go against React for the web, as there are lot of older browsers to support and yeah, React Native is for the mobile app, if you are talking about it.

BlackDark commented 6 years ago

Why shouldn't React work for older browser? Transpilation shouldn't be a problem.

praveenscience commented 6 years ago

@BlackDark Well, IE 8! 😞

BlackDark commented 6 years ago

In my opinion it wouldn't be the best approach to stick to older technologies and not state of the art development (especially for frontend projects) just to keep such old (and unsecure) browser compatible.

I would vote for modern technologies. (You can still try to use portable solutions like Firefox or Chrome if IE is not updated to IE11 (for my projects i am starting i even consider dropping support for IE11 because IE is some crappy browser which causes so much trouble in every dimension -.-) )

praveenscience commented 6 years ago

@BlackDark Just because this project is too good, I was thinking the browser support should be a bit good. Also, I am more inclined to React, Meteor or other awesome State of the Art techs for my next new project. Just my 2 cents. 😄

fnetX commented 6 years ago

Please make sure not to overrate Docker support. Docker is really helpful and makes life a lot easier, but some projects dropped support for installation without docker. Docker is still not fully supported by every server system, especially by low-cost VPS machines.

rrjanbiah commented 6 years ago

@fralix Thanks for your note on Docker. We'll surely consider your feedback. Thanks