In my last post I spoke about some technologies for real time operations. In this post I would like to take it a bit farther and talk about making Domino a “Real Time Database“. I use that term rather lightly as there is no means of scheduling and prioritizing transactions thus Domino isn’t really real time, but only behaves as real time.
First off we developed an Event Bridge plugin that taps into Domino’s C API for events which are fired when documents are created,
Right after Collabsphere 2018 I was introduced to a couple of new technologies. These were WebSockets and Redis. I must say that since discovering these technologies my mind hasn’t settled even a little bit. This has opened up a whole new world of possibilities for DIG and other projects I’ve been working on. So, what exactly do these things do?
This technology has actually been around for a while, but I’ve never had the time or thought I had the need to investigate it.
Part 1 – node.js and Domino
So that leaves to question, what can we do with it? Well, we can do a whole lot with it actually.
With the recent announcement of upcoming node support for Domino, I think we need to start looking into what it takes to get into node.js development. The truth of the matter is, it’s not really that difficult. To start with you need to install node.js. Then find a decent editor (I recommend Visual Studio Code).
Once you’ve got these things, create a new project directory somewhere (I’m gonna use hello-world).
I am honored to announce I will be presenting along with the Red Pill Now team at Engage in Rotterdam. My session will be:
Dev06. Reusability is the goal!
Wednesday, May 23 | 11:30 – 12:30 | E. Sky Room
a single line of code.
Here is our our now-confirm-dialog which shows up in the center of the screen:
The goal of this element is to provide a simple confirmation dialog and then have the ability to do something based on which button the user clicked.
Here lately I’ve been writing a lot of tooling in preparation for upcoming projects. This tooling is meant to lessen the amount of work to start up a new project. A while back I watched this video. That video inspired me to come up with a repository in which a front-end developer could clone, run a couple of commands and be ready to write code for the new project. Going down this route has been quite the eye opener to the complexity of what a modern progressive web app is today.
As web developers the ability to troubleshoot a web application is a very important part of the development process. To be able to see what’s happening and understand what may be causing a certain behavior is key and should be employed during the entire development process, not only when something is broken. In this series I will outline my process of troubleshooting web applications.
First off the tools. While there used to be a hand full of tools you might use now you only need one,