Cloud Migration for large ETL Application

%3CLINGO-SUB%20id%3D%22lingo-sub-708236%22%20slang%3D%22en-US%22%3ECloud%20Migration%20for%20large%20ETL%20Application%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-708236%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20organization%20is%20just%20beginning%20a%20long-term%20project%20to%20Migrate%20to%20Cloud.%20My%20department%20runs%20a%20set%20of%20applications%20that%20use%20ETL%20as%20the%20primary%20technology%20for%20performing%20a%20nightly%20batch%20and%20Java%20to%20power%20a%20User%20Interface%20to%20the%20data%20during%20work%20hours.%20The%20size%20of%20our%20primary%20database%20is%20%26gt%3B%2010%20TB%2C%20and%20that%20size%20is%20maintained%20only%20by%20aggressive%20Archive%2FPurge%20cycles.%20During%20an%20average%20nightly%20batch%2C%20we%20are%20shuttling%20%26gt%3B%201%20TB%20of%20data%20between%20the%20DB%20and%20ETL%20servers.%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20question%20is%2C%20would%20anyone%20even%20consider%20moving%20just%20the%20database%2FUI%20for%20an%20application%20like%20ours%20to%20the%20Azure%20Cloud%3F%20The%20ETL%20application%20we%20use%20is%20not%20Azure%20friendly%2C%20and%20our%20batch%20code%20complex%20enough%20that%20converting%20to%20another%20platform%20could%20take%20multiple%20years.%3CBR%20%2F%3E%3CBR%20%2F%3ECan%20Cloud-to-Premise%20data%20transfer%20rates%20support%20the%20kind%20of%20large%20data%20extracts%2Fwrites%20that%20a%20nightly%20batch%20like%20ours%20requires%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-708236%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20Architecture%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESplit%20Cloud-Premise%20Application%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-709379%22%20slang%3D%22en-US%22%3ERe%3A%20Cloud%20Migration%20for%20large%20ETL%20Application%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-709379%22%20slang%3D%22en-US%22%3E%3CP%3EAzure%20can%20absolutely%20support%20this.%20In%20my%20opinion%20the%20best%20way%20to%20accomplish%20this%20is%20to%20leverage%20an%20Express%20route.%20This%20is%20a%20private%20connection%20between%20on%20premises%20and%20Azure.%20If%20you%20workload%20is%20currently%20on%20premises%20and%20not%20in%20a%20datacenter%20you%20will%20have%20to%20work%20with%20an%20ISP%20to%20establish%20this%20circuit%20working%20through%20an%20data%20exchange%20provider.%20If%20your%20servers%20are%20sitting%20in%20a%20datacenter%20you%20could%20see%20if%20they%20are%20a%20data%20exchange%20provider%20and%20the%20circuit%20setup%20is%20much%20more%20streamlined.%20In%20the%20link%20below%20you%20will%20see%20you%20have%20a%20few%20options%20metered%2C%20unlimited%2C%20and%20direct.%20As%20you%20can%20see%20the%20speed%20is%20there%20in%20all%20three%20just%20depends%20on%20the%20pricing%20model%20you%20wanting%20to%20use.%20The%20metered%20plan%20may%20get%20really%20expensive%20if%20you%20are%20sending%201TB%20of%20data%20over%20the%20wire%20nightly.%20Hopefully%20that%20was%20helpful.%20I%20would%20be%20happy%20to%20answer%20any%20follow%20up%20questions%20you%20may%20have.%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F363190%22%20target%3D%22_blank%22%3E%40DougW659%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

My organization is just beginning a long-term project to Migrate to Cloud. My department runs a set of applications that use ETL as the primary technology for performing a nightly batch and Java to power a User Interface to the data during work hours. The size of our primary database is > 10 TB, and that size is maintained only by aggressive Archive/Purge cycles. During an average nightly batch, we are shuttling > 1 TB of data between the DB and ETL servers.

My question is, would anyone even consider moving just the database/UI for an application like ours to the Azure Cloud? The ETL application we use is not Azure friendly, and our batch code complex enough that converting to another platform could take multiple years.

Can Cloud-to-Premise data transfer rates support the kind of large data extracts/writes that a nightly batch like ours requires?

1 Reply

Azure can absolutely support this. In my opinion the best way to accomplish this is to leverage an Express route. This is a private connection between on premises and Azure. If you workload is currently on premises and not in a datacenter you will have to work with an ISP to establish this circuit working through an data exchange provider. If your servers are sitting in a datacenter you could see if they are a data exchange provider and the circuit setup is much more streamlined. In the link below you will see you have a few options metered, unlimited, and direct. As you can see the speed is there in all three just depends on the pricing model you wanting to use. The metered plan may get really expensive if you are sending 1TB of data over the wire nightly. Hopefully that was helpful. I would be happy to answer any follow up questions you may have.

 

https://azure.microsoft.com/en-us/pricing/details/expressroute/

 

  @DougW659