I'm in 10000% agreement with you on REST. REST, as currently implemented, is pretty difficult to make "robust" in a way that an experienced enterprise person would think of it. I mean... it's better than "I have a cron job that calls SFTP to check for new CSV or tab-delimited files that were exported from the DB2 server, and downloads them and then imports them into a staging table and then runs another batch job to sync them to our 'source of truth' tables" but... but yeah.

As a whole, I am just so utterly disappointed in this industry. Was SOAP perfect? Not by any means. But at least I didn't have to GUESS at the possible data types coming through. REST (assuming we're talking about a JSON package here) doesn't give me that comfort levels, the folks pushing it seem to assume that the destination is always something that is not strongly typed, and in the world of enterprise development, that is very rarely the case. It's much more likely to end up in DB2 or Oracle or something than, say, Mongo DB... it's just as likely to be processed by COBOL or Java as Python or JavaScript.

But I'm an old fuddy duddy with a greybeard (well, when I don't use my Just For Men :D ) and who learned BASIC in the days of line numbers, using classic vi as my editor... so what do I know?

J.Ja