Entries tagged [innovation]
New product for Domino keyrings: Aperture
by Richard Pajerski
Posted on Monday July 20, 2020 at 11:23AM in Technology
Since many development and administrative tasks in Notes/Domino can conveniently be carried out with great front-end tools like Domino Designer or Administrator, it can sometimes be inconvenient when we're required to use the command line or terminal to get things done. Working with Domino keyrings is a case in point and one of the reasons why I developed Aperture.
Aperture is a lightweight desktop application that allows you to work with those .kyr files without having to resort to the command line. It works with both the KYRTool and OpenSSL to allow you to visually create keyrings, view their contents, create Certificate Signing Requests and several other tasks you'd normally being doing on the command line.
Please visit the Aperture product page for more details: https://www.rhpconsult.com/aperture.html.
As always, comments and suggestions are appreciated!
Tags: certificates domino general innovation notes software ssl tls
Multi-document transactions in Domino: needed!
by Richard Pajerski
Posted on Tuesday July 31, 2018 at 02:44PM in Technology
Among the areas getting attention in the upcoming release of Domino 10 is the data store. As part of making Domino more bullet-proof, removing the 64GB limit on the NSF size is planned and will be a fantastic improvement. Naturally, this is going to put more emphasis on overall database scalability. As Domino gets more scalable, I think it's going to need a feature that many of us have been seeking for some time: multi-document ACID transactions.
Being able to save two or more documents as a single transaction cannot currently be done natively in Domino. The best we can get is saving all of the fields associated with a single document using NotesDocument.Save: the operation either succeeds or fails. This is fine for most Notes/Domino applications but there are a number of cases where having a transactional save across multiple documents is desirable. A simple work order system where multiple, related tasks are attached to a main work order request is an obvious example. Implementing each task as a separate document is an intuitive approach and can simplify programming of such a system.
MongoDB 4.0 recently introduced multi-document transactions. And although Domino doesn't directly compete with MongoDB or other NoSQL databases, as it begins to scale, it's nonetheless going to need to act more like them.
What do you think?
Tags: database domino innovation