News for hackers. Stuff that matters.

A comment on The 2002 mandate for internal communication systems at Amazon. Parent comment

Re:The 2002 mandate for internal communication systems at Am... by jhallenworld on Tuesday October 01, 2019 @04:18PM (#21130115)
IBM has an appliance for you:

https://www.ibm.com/products/datapower-gateway

It's a middleware appliance that allows any API to talk to any other API and handles just about any data format. You can script it with javascript or XSLT. It can handle ad-hoc things like ftp polling.

It has the added benefit that you can add security for outside facing clients.

Disclaimer: I helped develop this appliance (but I no longer work for IBM)

[ Parent | on HN ]
Re:The 2002 mandate for internal communication systems at Am... by flukus on Tuesday October 01, 2019 @07:59PM (#21132181)
Pricing: Contact Us.

So basically it will be expensive, require an army of IBM consultants and become yet another integration point instead of actually solving anything.

[ Parent | on HN ]
Re:The 2002 mandate for internal communication systems at Am... by jugg1es on Tuesday October 01, 2019 @11:19PM (#21133185)
IBM's business model is totally antiquated and exhausting for modern processes. We have had a nightmare trying to get IBM MDM's solution to finally admit they were not actually cloud-ready after saying repeatedly that they were. No TLS support for DB2 out of the box for K8 support, documentation sucks. But contact us for pricing. IBM sucks.
[ Parent | on HN ]
Re:The 2002 mandate for internal communication systems at Am... by nameistaken on Tuesday October 01, 2019 @11:18PM (#21133184)
Cries in Webseal.
[ Parent | on HN ]
Re:The 2002 mandate for internal communication systems at Am... by closeparen on Friday October 04, 2019 @03:25PM (#21161029)
This is the Enterprise Service Bus concept, right? I remember a pretty good conference talk about how we realized in the mid 2000s that these things are problematic and you probably want services communicating directly over dumb pipes.

In showed an evolution from a monolithic spaghetti codebase, to an SOA, to realizing there are now spaghetti connections between services in an SOA, to a very clean looking ESB architecture, to showing how all the chaos is still there, just inside the ESB where it’s even harder to reason about or change.

[ Parent | on HN ]