We're developing a SaaS app in Java, built with Maven. It runs on Amazon on a (potentially) large number of servers. We'd like to deploy changes every day or two.
We have a ton of unit and system tests ready to go, and can run the Maven deploy command as needed.
This app operates on large data files that live on the local disk, so it's not going to be easy to create a new AMI and spin up new instances for each deployment. We'd have to copy gigabytes of data. That having been said, it would be nice to bounce the servers every once in a while so we migrate to newer Amazon hardware as it becomes available.
How can we best deploy updated versions of the software given the above constraints?
Aucun commentaire:
Enregistrer un commentaire