CODEWITHSUNDEEP
soa
NimChimpsky
NimChimpsky

Reputation: 47290

serivce oriented architecture (SOA), what to do when given one unit of work, which could really be two?

Within a SOA individual services should not interact with each other.

When given a requirement for one service, that could really be made into two separate services/units of work. What is the best action ?

Creating two, where service A contains both units, and service B contains only the "first" unit/service breaks DRY ? To clarify, where one is assumed to be dependent on the other the completely independent unit of work can be placed into its own service, and the two combined units can be placed in a second service.

Given a requirement for one service that can and maybe should be split into two, what should do do ?

Upvotes: 1

Views: 156

Answers (1)

Cratylus
Cratylus

Reputation: 54084

Perhaps I am misreading your OP but you can have a service B that exposes an interface for a specific functionality offered and a service A (or C or D for that matter) that consumes that interface to offer the specific functionality offered by A.
Services can use a functionality offered by another service via its interface. But they are not coupled, in the sense that the same interface could be implemented via a different set of services

Upvotes: 1

Related Questions