My mongo instance grew up to the RAM limit I've set to its container. What happens if it eventually reaches the limit? Crash? Performance decline? Or is it just dropping stale indexes?
Is it possible to wire up a small zero downtime deployment (*1) with two Amazon EC2 instances? I'd like to roll my services regularly to a new EC2 instance to avoid manual OS updates on the instances itself.
EC2-1: application serivces
EC2-2: database, consul registry for docker networking
EC2-1 would be the only public instance (bound to an Amazon Elastic IP). Shouldn't be a problem to replicate this one and change the Elastic IP to the new EC2 instance, right?.
However, I don't know if it is possible to switch EC2-2 as docker stores the docker-networking settings in the consul database. Can I start a replica of that instance and tell docker that it should now use the new consul instance for networking?
(*1) you can't guarantee zero-downtime in case of instance failures etc. with two instances. I mean zero-downtime while moving to new EC2 instances :)
let's say
1) I have a server running in a private intranet. It uses tomcat to serve a webapp at privateserverip:8080/appname
2) I have a myapp.local domain and when I enter it toplevel with http://myapp.local it serves the app from privateserverip:8080/appname if the request comes from within the intranet
That is the actual state.
Now: I have a public domain: example.org and I want that if a website redirects a user, who is in the intranet (!), to myapp.example.org, privateserverip:8080/appname should be served. If somebody from outside the intranet hits myapp.example.com nothing should happen.
Please tell me that this is possible!? :)
I could configure vhost in an nginx at example.com but also create DNS entries and stuff like that for example.com. Everything you want. Just tell me that this is possible
Thanks for your help :)