node node.js, domino-db & Docker (12): DominoDB and a big NO-NO? 

By Sven Hasselbach | 11/15/18 7:17 PM | App Dev - Web | Added by Oliver Busse

Disclaimer: This is a response on Heiko’s post about his security considerations with the domino-db module. It is good to have such a discussion, and hopefully this discussion will go on. This is my personal view on this topic. If you have another opinion, feel free to add a comment.

DominoDB and a big NO-NO ! 

By Heiko Voigt | 11/14/18 5:26 PM | App Dev - Web | Added by Oliver Busse

So folks, the beta of DominoDB is out and people are starting to use it. One of my early-adopting customers started to play around with it and started to create a React.-based application using DominoDb to modify database content. They secured their Proton task using the SSL encryption. So far so good. What I did not expect was the flaw in the architecture of the app that I came across when I looked at the source

The Changing Domino Environment Architecture - Intec Systems 

By Paul Withers | 11/12/18 4:33 PM | App Dev - Web | Added by Oliver Busse

This article has been prompted by my previous one on Domino application development. One of the major differences between Domino application development in the past and the approaches for Node.js-related development in the future is architecture. But part of that could also be an inhibitor for existing customers, because of the incubated world of Domino.

Whither XPages? 

By Paul Withers | 11/8/18 9:55 AM | App Dev - Web | Added by Oliver Busse

Some years ago I wrote a blog post called “Whither the Notes Client”. At the time (2012) XPages was flourishing, the Notes browser plugin (subsequently ICAA) was being launched, Symphony was being stopped and the IBM-specific enhancements routed back to Apache OpenOffice and iNotes was being integrated into what is now Connections Cloud.

Java Hiccups 

By Jesse Gallagher | 11/8/18 5:30 AM | App Dev - Web | Added by Oliver Busse

To take a break from the doom-and-gloom of my last post, I figured it'd be good to dust off a post idea I've had in my drafts for a while: common hiccups that Java developers - particularly those coming from a Domino background - run into. This is sort of a grab bag of non-obvious concepts that are easy to assume incorrectly about, whether because of the way other languages work or the behavior of the lotus.domino API specifically.