simonsaidit

Lets say you have this legacy spagetti of 100s of services and different data sources and you want to start thinking about a better architecture as there is a need to expose a lot of this data via apis and get away from point to point integrations. Its different databases, datawarehouses, transports. Its a a state Where people hardly know where to find the different data and there is a lot of duplikation and inconsistency. What would be worth looking into going forward to slowly transition to a somewhat standard way of handling integrations and data management.

Is there any buzzwords that would make this easier.

My own thoughts would be an integration platform, some api management product, event-sourcing architecture... Perhaps Kafka or similar, graphql api.

There is no way of migration of data to to some master data format but is there ways to add a frontend on different databases eg postgresql external source and add graphql on postgres or does this sound crazy.

Is there data lake software, or graph databases that could load All this data in its own format and connect the dots or is the best still to leave it as it is and expose it via their own apis.

Any ideas are welcome.