3 ms·
This is one of the niches where (S)FTP and batch processing is still alive and kicking.
by adambyrtek 7y ago
This is one of the niches where (S)FTP and batch processing is still alive and kicking.
- mason55 7y agoYeah, SFTP + CSV file is still the standard for enterprise software. The problem is that these kinds of things have to be built to the lowest common denominator, which is usually the customer anyway. The customer in enterprise software is usually not a tech company they typically have outdated IT policies and less skilled developers than a pure tech company would have. Even if the developers are capable of doing something like interacting with a queue they also need to be supported by a technology organization which can deal with that type of interaction. Some times you get lucky and someone in the past has pushed for that kind of modernization. Or your project really won't work without a more advanced interaction model and you have someone in the organization willing to go to bat for tech enhancement. But otherwise the default is "Control-M job to consume/produce a CSV file from/onto an SFTP"
- deleted 7y ago[deleted]
- dfox 7y agoMy experience is that usual reason for RPC-over-SFTP is that it is the only thing that corporate IT security does not control and thus cannot make inflexible. Adding another SOAP/JSON/whatever endpoint tends to be multiyear project, while creating new directory on shared SFTP server is a way to implement the functionality in few hours.
- crtlaltdel 7y agoits also quite common in fixed data logging applications, such as exports from bms.