My previous job was to develop POS software that was marketed by SAP (we were a SAP gold or platinum partner - can't remember which). The POS software did not i

My previous job was to develop POS software that was marketed by SAP (we were a SAP gold or platinum partner - can't remember which). The POS software did not include the part that actually runs on the POS but also all the backend stuff like order management, inventory management, etc. So we were forced to use the crude SAP XML interfaces for data exchange (IDOCS) and it was really disgusting. We were also forced to use SAP NetWeaver which is a PITA to manage. Also, the customer decided to use POWER9 so we were also forced to use the SAP-maintained port of the JDK for POWER9 and we have found like 4 or 5 bugs in this port. Also, being a SAP partner, we were forced to use UI5 which is such a horrible framework. But the thing is, SAP is a freakin' huge company and the software is quite old. They are on the right track to make things better (XSA, other data exchange format). Another funny story is that some customers decided to host their system at SAP. The SAP department (SAP HEC iirc) that took care of updates of the systems planned with 14h per system per update - complete downtime. One customer had 3 systems at SAP, which meant that it took three Sundays until all systems were updated. Since then, most moved to OEDIV for hosting which does a slightly better job. SAP HANA (the DB) is quite cool though. We had one with 4TB RAM and it was super fast.