In the beginning of a Oracle based/ scoped Web project we have to take a decision whether to go the conventional ADF path or tread the now trending JET path.
Many a times we get lured by the latest cutting edge technologies and incline towards that. However I would like to share my learnings in this scenario.
I feel JET is more apt choice :
a. If the application is accessed from mobile devices ( responsive applications ).
b. If it is not a very data intensive application. We can tap the full power of JET if user acts on limited set of data. That is the data is already fetched and the data is manipulated in the ViewModel layer.
c. If application uses third party Javascript libraries. Ex: cordova plugins, Camera feature, QR code scanning etc
d. The Oracle JET community is very proactive and we can expect help whenever we are in an issue.
I feel JET is not a appropriate in below scenarios :
a. If the UI needs to show data from multiple sources. In such cases we need to go with Master-Detail screens, Cascading LOVs.
This becomes timetaking specially when all the sections are based on different sources ( Ex: REST services ) and the onus is on developer to handle the dependencies, filtering, sorting, searching. etc. I wish if JET could also come up with the
b. If we need Search region, Advance search region, table level filtering, table level sorting etc there needs to be extensive coding to be done. If the project timelines provide enough bandwidth then this additional task can be compensated.
c. Even though there are a vast number of JET Visualizations are available in JET, to feed these components with the data in appropriate format, it needs lot of data massaging which means more time obviously.
d. If the OAuth needs to be implemented more time needs to be pumped in, as it is different from SSO or weblogic based authentication.
Finally as ADF is around for a long long time, all the features are matured enough and in a tight time lined project this allways proves to be a better choice.
Given the extensive documentation, Blogs and Support we are not stuck at particular issue.
Though I have shared my experiences, it is upto the requirement of the project and ofcourse the client preferences !! :)
Thanks for reading,
Srikanth
Many a times we get lured by the latest cutting edge technologies and incline towards that. However I would like to share my learnings in this scenario.
I feel JET is more apt choice :
a. If the application is accessed from mobile devices ( responsive applications ).
b. If it is not a very data intensive application. We can tap the full power of JET if user acts on limited set of data. That is the data is already fetched and the data is manipulated in the ViewModel layer.
c. If application uses third party Javascript libraries. Ex: cordova plugins, Camera feature, QR code scanning etc
d. The Oracle JET community is very proactive and we can expect help whenever we are in an issue.
I feel JET is not a appropriate in below scenarios :
a. If the UI needs to show data from multiple sources. In such cases we need to go with Master-Detail screens, Cascading LOVs.
This becomes timetaking specially when all the sections are based on different sources ( Ex: REST services ) and the onus is on developer to handle the dependencies, filtering, sorting, searching. etc. I wish if JET could also come up with the
b. If we need Search region, Advance search region, table level filtering, table level sorting etc there needs to be extensive coding to be done. If the project timelines provide enough bandwidth then this additional task can be compensated.
c. Even though there are a vast number of JET Visualizations are available in JET, to feed these components with the data in appropriate format, it needs lot of data massaging which means more time obviously.
d. If the OAuth needs to be implemented more time needs to be pumped in, as it is different from SSO or weblogic based authentication.
Finally as ADF is around for a long long time, all the features are matured enough and in a tight time lined project this allways proves to be a better choice.
Given the extensive documentation, Blogs and Support we are not stuck at particular issue.
Though I have shared my experiences, it is upto the requirement of the project and ofcourse the client preferences !! :)
Thanks for reading,
Srikanth
No comments:
Post a Comment