Ask HN: Best Architecture Patterns for Integrations?
Hey all, anyone here have personal experiences or resources to share on how companies have successfully approached designing an architecture to handle N integrations syncing down into one application?
More often than not I've seen these systems designed around an inheritance structure which frankly I don't agree with -- given enough time integrations will diverge enough that the once "shared" functionality no longer applies and you end up with a mess of inherited methods and overridden function chains.
I'm not _really_ sure what the alternative to OOO + inheritance is in designing an integration system though, Events? CQRS? Etc?
More often than not I've seen these systems designed around an inheritance structure which frankly I don't agree with -- given enough time integrations will diverge enough that the once "shared" functionality no longer applies and you end up with a mess of inherited methods and overridden function chains.
I'm not _really_ sure what the alternative to OOO + inheritance is in designing an integration system though, Events? CQRS? Etc?