we are currently doing a project in which RFC's are called from an external facing portal. We have identified several services (rfc's) which will have to be developed. Now, in stead of creating for example two separate services for create and update (of BP for example), we want to 'merge' those two into one service. Depending on some criteria the BP will be created or updated. Now, in light of eSOA, I was wondering if this is the way to go? Meaning, does it make any difference to create two separate services or just one which fullfills both tasks.
They're both services which can be reused, so as far as I'm concerned this would fit right into a service oriented architecture...or is this is bit too simplistic?