Dear community,
I started look in and dig in to airavata-django-portal to start work on the
desktop application for airavata. But, my current understanding about the
airavata django portal is, it's a good idea to redesign it. Few point to
say like that is,
- REST api
- There's improvements needed on the auth flow.
- Endpoints are only session based and does not support token based
authentication or authorization.
- Some of the endpoints are redundant and I would say the design can
be better.
- Front end
- I feel it's better to have the front end application as a
separate application connected to the rest api. So, that it can
be managed
separately plus customisations can be done irrespective of the api.
- Considering the components reusability between desktop application
and web application, the architecture can be redesigned.
Considering the project I would say, it's better to think of the long term
approach rather adding up some more code which means for refactoring. Few
more additional points I would like to add are,
- Storage management is a common requirement not only for airavata
portal but also in general. For an example, the election project i'm
currently working is also having such requirements and actually we also
have built something on our side. But, if we could generalise it to a
common component, it could be reused.
- Since this api is meant for the clients to consume directly, it'll be
better to have some kind of more documentation as in like open api spec for
an example. So, that they could play around with it.
Actually this is my understanding for few weeks and I would like to have
your thoughts and advices.
Regards,
Dinuka
