Engage 2018: My Session
A couple of weeks ago I presented at Engage on developing a React app using Domino as an API gateway and database. The slides are similar to the ones from IBM Think, just a few changes and rearrangements, so they are only posted on the Engage website.
There are a few aspects I forgot to mention.
- The source code can be found on GitHub and, since IBM Think, I’ve been through the React app and commented it in depth.
- To reiterate what I have said in the sessions, the architecture we use is deliberately not straightforward. We didn’t want a “Hello World” type demo, we wanted something closer to approximating a production environment. So there are additional technologies like Kubernetes, Istio and Agilit-e which add complexity . They may be overkill for a small app, and certainly for a demo app. But they are definitely relevant for a business-critical high-availability application where you want to better manage migrating through development, test and production environments.
- The editor for Node-RED we use is authenticated, as you would want it to be in a production environment. Authentication is against the same Domino server where the database resides. As we said, Domino is the master, not just another NoSQL database.
- Node-RED was contributed as open source by IBM.
- I used Visual Studio Code for reviewing and amending the React app, WebSocket server and Agilit-e server. This was the preferred IDE for developing web applications at that same HCL/ICM session.
As with many sessions I’ve been involved in, this has been very informative and has taught me a great deal that I’m sure will be useful over the coming years. It’s opened up a lot of potential for applications or microservices, whether on premises or on the cloud.