You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think down the line, it would be ideal if Migratekit runs as an agent, and then another service talks to it. There are some sort of networking problems we would have to think about to make sure the case when the two systems cannot talk to each other directly.
I agree. I general the architecture could look something like this.
Deploy an "agent" in the source and Destination. They should then register to a central system which is reachable just with public HTTPS which makes deployment way easier. Then the central component can talk to the "agents". Relaying the traffic over the central point could also make it easier.
This sorts out most of the networking problems. Using something like https://github.com/jpillora/chisel has proven to be very effective in the past. Queueing and job management could happen centraly.
This require some engineering but with the help of claude 3.5 sonnet most of the heavy lifting is only a proper design.
It would be great to have a webui for migration kit to simplify the usage.
The text was updated successfully, but these errors were encountered: