#General software design advice

4 messages · Page 1 of 1 (latest)

valid crown
#

I need to decide how to handle the following:
someone has made an API that gives access to stuff like suppliers, clients, purchase orders on his server.
I need to get this data and then move it to another system.
I was thinking Id use a servlet, the other person would send a call to it when his data changes and then that would trigger my code to get the new data and send it to the other system.
Should I use Spring for this? can it help?
He will probably have different objects for supplier, client, purchase order etc...
I need to grab the data, run some validations on it and then upload it to another system.
How should I generally design this?

real needle
#

Spring makes that kind of stuff pretty easy imo

#

in case one of the system makes a request to your service (the thing in question, just create an endpoint there that requests the data from the other service and transforms it)

#

if you want to run that thing explicitly, you might want to look at Spring batch