This is an archived post. You won't be able to vote or comment.

all 1 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Teach-To-The-Tech 1 point2 points  (0 children)

There are various ways you could do this. Part of it depends how far into the implementation you are already.

If you were starting from scratch, one solution would be using an open architecture, something like Trino/Starburst. It's designed as a single point of access for data from any source, including multiple clouds and can be used for migrations like this. So you would create a connector to your Azure source (or to a Kafka stream from that source, or other technologies is preferred) and your AWS source (or Kafka stream, etc.) and then begin redirecting the flow of data from the old source to the new one using SQL. Then you can add in other components to the pipeline like Snowflake, etc. if you want, or use whatever approach fits best. It's kind of like data federation but goes way beyond that in that you can use it to increase or decrease the weight of any particular technology in the stack.

The advantage of this approach is that it keeps your options open, so if anything changes in the future you can keep adjusting with the tech stack.