Replies: 5 comments 1 reply
-
Use AWS. Sorry, it's like a wet paint sign or when the waiter says "the plate is hot". |
Beta Was this translation helpful? Give feedback.
-
Any reason AWS is better than Azure? |
Beta Was this translation helpful? Give feedback.
-
My employer is currently making this migration. I am NOT a devops person at all. My perception as an application engineer is that this migration from AWS to Azure is made easier because the company has generally standardized on k8s. So with docker images tuned the way we want them and helm charts and terraform, it is in theory deployable or easily migratable to almost any cloud vendor. Some decisions when running in Azure are what common apps to standardize on. Some examples:
This migration has also been a chance to catch up on some tech debt. My team is defining our Mirth images the way we want, not the way some devops engineer guessed (I say that lovingly and respectfully!). We're using more environment variables. We don't have persistent storage beyond the database. We have our plugins set how I want them as a Mirth expert. I don't know how much that helps. Anecdotes != data. |
Beta Was this translation helpful? Give feedback.
-
I think they are leaning toward sql server as they already have the licensing for that in Azure. Not sure about AD. I don't think there is anyone on the team that even knows how to set up the VM or Mirth image. I suspect they will be utilizing a 3rd party to help with the architecture and initial setup. |
Beta Was this translation helpful? Give feedback.
-
Regardless of your cloud vendor - the infrastructure behind mirth and familiarity with designing and troubleshooting it should be paramount. For example, if you need IPSec tunnels - who will build those? If you need public facing API endpoints, what tech will you choose? WAFs, IDS/IPS, cloud posture management and so on. The list can be very long and it is not a "set it and forget it". You need resources assiged to maintaining your infrastructure like you would for an in house deployment. |
Beta Was this translation helpful? Give feedback.
-
We are embarking on a project to move our Mirth instances to Azure. Would appreciate any recommendations, experiences, things to consider or gotcha's. Any problems you might have run into. Thanks
Beta Was this translation helpful? Give feedback.
All reactions