4 ms·
Assuming the application code is mostly stateless (it pulls all the data it needs from the database on every request), this kind of app is usually not a big dea
by ElevenLathe 4y ago
Assuming the application code is mostly stateless (it pulls all the data it needs from the database on every request), this kind of app is usually not a big deal to containerize and put on some cloud platform (AWS, GCP, Azure should all be about equivalent) and even get more 9s and scalability almost for free. This is essentially the Wordpress architecture, which every infra engineer (née sysadmin) in the industry has been asked to move from on-prem to cloud sometime in the past ten years.
If the application code has non-disposable state in-memory then it's bit harder but can usually be done, especially if it's low-traffic enough to comfortably live on single Rackspace dedi now.
Edit: I should also mention that if you're looking for somebody to do this kind of work for you, there are contact details in my profile. ;)
- angst_ridden 4y agoI'll have to look into the web-server customizations. One of them has a custom Apache module for talking to a 3rd party mainframe, but that should theoretically be movable too (if it's the correct platform architecture). Of course, an Apache module's just C code, so how hard could it be to port to another architecture? But in all seriousness, I suspect it's a relatively simple UDP socket communication interface, so it is probably portable. Thanks for the mention of Wordpress. It is a similar architecture. I'll read up on how to move a Wordpress install, and use that as a model for testing one of these apps.