Re: Hosting a Large Number of Node Apps on the IBM i

Aaron,

Thanks. That makes sense. And I agree that our users are increasingly
wanting (or needing) non-CRUD apps to stay efficient and effective.

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
1.217.773.4486 ext. 12676
kcookson@xxxxxxxxxxxx

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Aaron
Bartell
Sent: Thursday, October 15, 2015 9:07 AM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Hosting a Large Number of Node Apps on the IBM i

But what exactly do you mean when you contrast a vanilla CRUD app with
a

better user experience?

The below article is a CRUD app I wrote in Node.js. CRUD apps are mostly
for traversing the database relationships. For example, display customers,
select specific customer, select customer orders, display specific order.

http://www.ibmsystemsmag.com/ibmi/developer/general/creating-crud/

In contrast, a non-CRUD app would bring you to a dashboard showing the
latest orders, the orders with issues, customers with outstanding money
issues, etc. In short, non-CRUD apps incorporate many DB2 tables and
business logic into a single screen to keep the user efficient. CRUD apps
are more for allowing you to maintain data on a table by table, screen by
screen, basis.

That's my view of CRUD. I am sure there are many other flavors of views.

Aaron Bartell
litmis.com - Services for open source on IBM i


On Thu, Oct 15, 2015 at 8:59 AM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:

Aaron,

When I think of CRUD, I simply thing of operations against a database
table. A RESTful service can perform create, read, update and delete
operations against a table with no user interface defined.

When I hear the phrase CRUD app, I think of a green screen that allows
you to take some options against records in a display file. I know I
don't want to develop web pages and mobile apps that resemble green
screens. I could just use a screen scraper to do that--and then have
users wonder why we switched from green screens, and why my web pages
don't work like the web pages they view on the Internet. I get this.

But what exactly do you mean when you contrast a vanilla CRUD app with
a better user experience?

Thanks,

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
1.217.773.4486 ext. 12676
kcookson@xxxxxxxxxxxx

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Aaron
Bartell
Sent: Thursday, October 15, 2015 7:55 AM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Hosting a Large Number of Node Apps on the IBM i

I can understand the need for generated REST services (great for
Javascript
front-ends) but was surprised to hear you espouse CRUD. In my
experience the vanilla CRUD apps (even for internal use) are losing
ground (as they
should) because a better experience is being demanded by both
customers and employees. I think this is where WebSockets are really

going to shine.

Are others still seeing CRUD apps as acceptable (from the
customer/employee perspective)?



Aaron Bartell
litmis.com - Services for open source on IBM i


On Wed, Oct 14, 2015 at 2:59 PM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

Kelly

you never know what you run into, my web-systems runs side by side
with a varity of products.

btw, I am able to publish 600 tables with the same amount of generic
REST/CRUD services in less than 5 minutes by using my SDK - how long
do you think it will take to hand build the same in node.js?

On Wed, Oct 14, 2015 at 8:42 PM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

and developing custom web and mobile apps for our employees to
perform their business processes.

Soon after you make the move to Web interfaces, you won't be
constrained

to

only supporting "employees". Most shops branch out to supporting

customers,

trading partners, and providing greater variety of Web services
across

more

application areas.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at

http://archive.midrange.com/web400.

--
Regards,
Henrik Rützou

http://powerEXT.com <http://powerext.com/>
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list To post a message email: WEB400@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.