Re: opinions - utilizing more of what the i has to offer -- MIDRANGE-L

Hmmm insightful Nathan. Thank you.
I’m willing to bet this is their exact mindset behind going with Mulesoft.

Jay

Sent from my iPhone

On Feb 3, 2020, at 4:06 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I get the impression that Mulesoft engages at the CIO level because their
sales pitch and the scope of their Anypoint Platform is for the entire
enterprise and data exchange partners. Large enterprises generally have a
lot of silo'd systems and databases that would benefit from web-service
integration. The sales pitch is for a single platform that integrates them
all, using the same tools and interfaces. That includes a centralized
repository for every team on every silo'd system to document and publish
their web services, build a web-service ecosystem and community. If that
was the reason for acquiring Anypoint Platform, then I can see how the
powers that be might push back on a competing alternative. If that's what
happened, maybe the best one could do would be to build or buy an IBM i
"connector" for Anypoint Platform. One that would facilitate the interface
between your IBM i applications and databases and Anypoint web services.

That said, the whole movement to web services was something of a rejection
of ESB architecture. Under an ESB paradigm, silo'd systems are required to
communicate with an ESB and accept callbacks from the ESB. Web services in
contrast had silo'd systems implementing their own HTTP servers and
accepting connections from any client. The middleman (message broker) was
eliminated under the web-services paradigm. If a silo'd system were down,
then connection requests from clients would simply fail, and the client
would have to try again later.

On Mon, Feb 3, 2020 at 12:21 PM Evan Harris <auctionitis@xxxxxxxxx> wrote:

If you are using an ESB like Mule it makes a certain amount of sense to
centralise and organise communications through it.
Have a large number of directly communicating systems can quickly become
very hard to unravel and manage when things change. Organising all data
exchanges through the one broker can help unravel this.

Take for example, a situation where system a is communicating directly with
system b.
If system b is replaced with system c, then both system a and system c
probably need to make changes.
With a broker then the changes should be confined to system c.
There's also the security aspect that if all external communications are
through the broker then (theoretically) it's easier to secure and manage.

--
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