Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • I've got the kind of feeling that the API plan will lead to more coupled systems, also from a development point of view. I feel more comfortable with a team developing an API backend for an actual DB. But I can't express this feeling properly as a technical decision Commented Nov 6, 2021 at 10:53
  • also what about adding more integrated systems? In case of events, it will be enough for the new system just to publish events in a standard way to the bus. Otherwise, I would need to expose an API, add the API call and modifying the merging part... Commented Nov 6, 2021 at 11:03
  • also, what about integration tests? if I have a BFF calling several APIs on external systems, I will need to run integration tests for all those systems. While with events, my platform will only care about its own frontend-backend integration Commented Nov 6, 2021 at 11:08
  • events vs api calling wont affect integration, either way you have work to do. tbh I would question the ability of random systems to push events, vs you programming a polling and conversion interface Commented Nov 6, 2021 at 11:45