Why choose Domino as your Web Application Server?

This is a blog that I have been wanting to write for a long time and it is very important to me as an developer and Evangelist of Lotus products. Many companies that I know have moved off Notes and Domino. Also I have heard many have come on board also. How the numbers stack up only IBM knows. But that does not matter if I am doing well in providing consulting services and training.

The thing that I have been struggling with and have not heard from IBM is a compelling story on why a company would what to use Domino as their Web application server versus Microsoft and Google solutions and more importantly open source solutions. First, if your company is a Lotus shop that makes sense. However, majority of the world is not when it comes to Web application servers. If Domino is going to turn the corner and grow as a Web application server which is the direction that IBM is pushing, we need to easily provide this compelling story. I see open source-based frameworks like Drupal and Joomla more and more prevalent.

For me there is a number of reasons I would use Domino including:

- Single Integrated Package with Application Server and Database
- Security Model
- Integration
- Flexibility
- NoSQL architecture

Comments

Palmi said…

Let me add to this list :
Easy deployment
Great community support
Xpages. With http://maqetta.org/ coming , we will have a Killer Application environment.

April 19, 2011 at 9:44 AM

Domino Interface said…

Palmi,

I thought about what you said. The easy deployment I would add in. Great community support applies to all the competitive platforms so that would not be a factor. Xpages though it is great from the Lotus community perspective, it just brings Domino closer to the level that other platforms already have. It is more of a "me too" and would not distinguish Domino over the other platforms.

Maqetta is interesting. Let's see how it can be incorporated into the Domino develop environment.

April 19, 2011 at 12:57 PM

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

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

Introducing iPhora Automate - User-driven Automation for Your Mission Critical Processes

By trade, I am an Electrical Engineer with a specialty in Microwave Engineering. And as part of my education, I had to take courses in process and industrial engineering which involved process optimization and automation. I hated these two courses and naively thought I would never ever use the information that I learned in these two courses. I only had interest in the technical aspect of engineering and with my first job out of college that is what I did. Never did I ever thought that I would spend the past 20 years focused on stuff that I hated in college. The concepts of iPhora came out of issues that we encountered as we rapidly grew another business many years ago from which spawn our business process automation business which we have been doing for the past 20 years. For the past few years, we have been transforming our consulting service platform into a commercial off-the-shelf product that focuses on the business user as the target audience. We would like to introduce iPhora Aut

Domino Interface

Search This Blog