So after the refreshing reality that is ROR I tried to remind myself of what it would take to get Java’s ORM Hibernate to to work with an in memory Database since mysql is memory inefficient (runs in the background of the development machine) & has too many configurations & unnecessary feature sets that are not useful in development. With in memory database you have the best of both worlds, you can mock up your DB & then migrate to an RDBMS when it is time to deploy & stress test. I have used ORMs (EOF, Hibernate) with Oracle’s RDBMS & IBM’s RDBMS (DB2) so I wished to see what it would be like with an in memory DB.
So the hooks were not so clear due to a lack of proper documentation (or so I thought).
When testing out ideas for the front end I often have to copy over the entire backend in ROR (which is convenient) but rather memory intensive.
So with class components there were a lot of connect method calls & calls to mapStateToProps & mapDispatchToProps along with the layers of indirection like actions and reducers.
So I was thoroughly confused with basics of React-Redux but managed to get the final project working somehow & even somehow had some semblance of clarity during the review (code review). But now that all the immediacy is in the past & redux and react etc. are less relevant things are not so clear. Thanksfully I was able to run into some sources which helped me create a very rudimentary hello world React-Redux app to allow me to grasp the essentials again (and hopefully may help others too).