I'm working on a system which uses SilverStripe with a whole bunch of custom data objects, and several other services that communicate with portable devices on some proprietary protocol rather than HTTP
Right now the code in SS digs around the database of the other service, and the other service digs around the SS database directly.
Is there a common way people create better interfaces between two PHP systems, particularly where SS is one of those? I guess the obvious approach is a REST interface over HTTP to silverstripe, and whatever makes sense depending on the other service implementation? While it'd be nice to manipulate SS objects directly from the outside, i guess it's quite nasty...
I'm quite a newbie to SS, so does anyone with experience of a system under load know - should I expect SS to handle a request over a REST interface to update an existing object and write it about 10 times per second? Of course to really know, I should prototype and try it, but it's also nice to know what to expect :)