|
I see it the same way.
Yes the rpg/sql devs write all the applications with related industry biz
logic to write the data to db2 database.
Why not let us handle the microservice end if it that simply serves the
data up to any off platform call!?
My guess is that before I came along the existing ibm i talent knew (and
still knows) very little if any at all in regards to cross platform
integration.
And decision was made upstream to not even bother training them.
Now they are heavily invested in Mulesoft, thinking that adding another
layer of NON ibm i architecture will help them better “extract” data from
the system.
Unfortunate
Jay
Sent from my iPhone
On Feb 2, 2020, at 4:48 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:programs that touch the data on the i? So you are looking at spending
As I understand it, real RPG programmers are still going to write the
money for a utility and teaching your staff an entirely new paradigm as
compared to spending a couple of weeks bringing your current staff up to
speed with your-already-paid-for IWS wizard?
projects? All it'll cost you is some hours and it might save you tons of
Why not take a week, maybe two, to try a few simple IWS web services
money.
are calling “powerhub”.
On 2/2/2020 3:33 PM, Jay Vaughn wrote:
Ahh. So Mulesoft is at the heart of what my senior leaders at my shop
really powerhub... I’d appreciate any opinions. Using Mulesoft (as a
So if anyone wants to revisit my original post, now knowing Mulesoft is
cheaper alternative) than doing web services (and basically all cross
platform processing) rather than directly from our IBM i applications in
native languages (and sql).
list--
Jay
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxquestions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
link: https://amazon.midrange.com
Help support midrange.com by shopping at amazon.com with our affiliate
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.