Skip to main content

The iPhora Journey - Part 14 - Bringing All the Parts Together

Welcome to the final post of "The iPhora Journey".

Our goal as we started this journey was to take the HCL Domino platform that we loved for more than 25 years and redefining a web application running on Domino. 

iPhora was created originally to allow us to provide a flexible platform for building secure web-based applications for our customers as part of our consulting services. However, it has now evolved into a platform that customers and partners can build their own solutions with the emphasis on user-driven workflow applications and process automation.

As an integrated application platform, you can build web applications in a variety of different ways with HCL Domino. In designing iPhora, we looked at the architecture of other platforms, identified their key features and determine how it could be implemented within the capabilities and limitations of HCL Domino and utilized its flexible architecture to the fullest.

We went through many iterations and versions always with a focus on continuous improvement. iPhora started with a pure JavaScript SPA/REST API architecture but as it evolved, we moved to a hybrid server-side generation/JavaScript REST API based architecture to provide better security and more control.

The entire architecture of iPhora is based on JSON which led us to create our own JSON parser written in LotusScript to meet our needs.  

During our journey, we created a few things:

  • MongoDB like JSON document storage and data management architecture
  • A high performance LotusScript JSON Parser that any JavaScript developer could understand
  • An entire server-side generation language
  • A flow-based platform for creating apps, workflows and processes
  • PhoraScript a JSON-based scripting language
  • Flow-based ActionStreams 
  • Dozens of custom Dojo-based widgets
  • An easy-to-use iPaaS platform 
  • Data connector architecture
  • A new data security model that leveraged the existing capabilities of Domino security
  • A secure community-based platform for isolating and running applications and processes
  • A no-code platform for creating apps and workflow processes
  • Command JSON language to install and configure iPhora automatically onto a Domino server

For the past two years we have been focused solely on moving it from being a consulting tool to a commercial product.  It has been challenging but fun.

As we end this journey, we are starting a new one. So, look forward to many announcements and things to come.

The iPhora Journey - Part 13 - Automating the Automate
The iPhora Journey - Part 12 - Bring the Public Cloud Experience to your Private Environment
The iPhora Journey - Part 11 - Integration to Cloud-based Services for Business Users Made Simple
The iPhora Journey - Part 10 - ActionStream - the Heart of iPhora
The iPhora Journey - Part 9 - Flow-based Programming for Your User Interface
The iPhora Journey - Part 8 - Flow-based Programming
The iPhora Journey - Part 7 - Transforming Domino with Microservices
The iPhora Journey - Part 6 - An Application, Rethinking and Redefining
The iPhora Journey - Part 5 - Dammit Jim, I'm a LotusScripter not a JavaScripter
The iPhora Journey - Part 4 - JSON is King - The How
The iPhora Journey - Part 4 - JSON is King - The Why
The iPhora Journey - Part 3 - Creating an Integrated UI Framework
The iPhora Journey - Part 2 - Domino, the Little Engine that Could
The iPhora Journey - Part 1 - Reimagining Domino


Labels:

Comments

Post a Comment

Popular posts from this blog

The iPhora Journey - Part 8 - Flow-based Programming

After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era).  But in the last decade, there a...
Post a Comment
Read more

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets".   As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, http://dojobootstrap.com. Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select...
Post a Comment
Read more

The iPhora Journey - Part 3 - Creating an Integrated UI Framework

The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework There are many ways to create the user interface (UI) for a web application. The HTML page could be created on the server and then pushed out. It could be static with the data generated on the page by the server with JavaScript, providing a more dynamic experience, or the server could generate new HTML content to update portions of the web page. XPages or PHP are good examples of this. Another method is to have the web page partially generated by the server and have JavaScript build the rest of the HTML by pulling data from the server via an API. This is the approach used in the Single Page Application (SPA) model. In all cases, it is still dependent on the web server technology being using.  As mentioned previously in this blog, XPages is dependent on complete integration between form and document, whi...
Post a Comment
Read more