If you haven’t done so, please read my first blog in a series about low-code called, “I Remodeled My Kitchen, and I Joined HCL. (One of These Things Was a Bad Decision.)” to see how Domino relates to me and my decision to get a new kitchen. Yes, this time , I was going to write about the Ford Pinto and how it relates to Outsystems (read previous blog), but something happened during the last two weeks that I had to write about. And, frankly, I need your advice.
We had waited for four months for the final two appliances for our new kitchen — a coffee machine and a dishwasher. When we called for an update from the company, we were told that shipment was delayed until February (the global supply-chain issues discriminate against everyone). So, we canceled the order and decided to keep the appliances we had — ones we’d had for years and were high-end when we first got them. We called a technician to see if someone could inspect them to make sure they were still in good working order, and upon inspection, everything turned out to be in perfectly good order. We were told they needed a bit of regular TLC and that they would last forever because they were designed and built to last. The kitchen still looks great, and we saved thousands of dollars.
The combination of the old and the new made me think about how the parallels could be drawn between my kitchen and HCL Domino. Just like my older appliances, Domino was built to last, has been rock-solid from the beginning, and when it’s integrated with more modern technologies, it produces an IT solution with amazing results — that is far less risky than a whole “rip and replace” — with an overall lower total cost.
As I research Domino competitors such as Mendix and Outsystems, one thing becomes very clear. They are not, in fact, a “full kitchen” solution. They are merely a “single appliance.”
Those companies are basically one-trick ponies with one product, while a company like HCL has dozens of products that can be integrated together to build an amazing “kitchen” that’s exactly to your specifications. This means that companies like Outsystems and Mendix need to rely on third-party products over which they have no control, which makes them inherently insecure, and we all, unfortunately, know what can happen in that scenario.
Volt MX — which is surrounded by dozens of other HCL products such as Domino and is supported by a massive global services arm — is a multi-experience low-code platform that is high up on the Gartner Magic Quadrant and directly competes with Mendix and Outsystems.
Imagine having tighter integration between Volt MX and the legendary Domino, so you can easily create mobile and progressive web apps (or even wearables or kiosk experiences) that connect to your essential core back-end business apps and workflows.
Imagine quickly and effectively modernizing and further extending your existing Domino apps by allowing your organization to create apps of the future on any device with Volt MX — which leverages all modern technologies — while still being able to rely on the security, governance, and workflow of Domino.
My point is that HCL has vested massively in Domino’s future and continues to do so. More importantly it is also investing how it’s products such as Volt MX can integrate with Domino and leverage each other’s market leading strengths. This is why when some people compare Domino to Alcatraz, I think that they are being a bit myopic and are not truly seeing the big beautiful low-code/citizen-code picture where both products shine and are even brighter together.
I see Domino has the critical power behind a composable, modern “kitchen” — with the addition of some key, amazing “appliances” from HCL’s extensive product line — to really elevate your game and get your business “cooking.”
This powerful combination would create a key competitive advantage. More importantly, I want to excite any IT decisionmakers who may have given up on Domino, or are still on the fence, and show them the bright Domino future that we all know exists.
Well, that is exactly what HCL is able to do. Check out how Domino forms convert to Volt MX forms and how Domino data can be accessed and surfaced (as can any other data source). This is not your father’s Alactraz!
Tighter Integration Between Volt MX and Domino
All of this leads me to my humble request from you. Do you think that Domino and Volt MX is a good idea? Please answer the LinkedIn Poll question below and please, please, please put something into the post’s comment. As you probably know, you can see the poll metrics in real-time.