Similar thing happened to me.. went through a very lengthy interview process and successfully passed it where they called me the day after and said that they were going to give me an offer the next day! I was ecstatic.
They then called me the next day and said "oh, yeah -- we aren't going to give you an offer" and wouldnt give me a reason.
The next time, they attempted to recruit me for the same position and I went through several days of phone interviews passing each one. Then I said -- "so you know, I interviewed for this position before and was told I would get an offer, but then didnt" they went back and checked and then said "Yeah we wont be continuing the interview process"
Then it happened a third time! Finally I sent the recruiter an email that said "This is the third time you have attempted to recruit me for this position -- Either offer me the job, with a salaray of X or take me out of your system and stop calling me"
They haven't called me since -- and I still have no idea why I am blacklisted.
I think he means before he told them to stop calling. It seemed like in the second interview after he said, "I already interviewed for this position," they suddenly wanted nothing to do with him for some odd reason.
The biggest issue that I had with ECS is that you need to initially create EC2 instances to put into your ECS cluster, using the AMI such that they have the ECS agent on them... BUT you have to prescale that cluster manually thereafter.
In the task definition - it would be MUCH better if you could select the EC2 instance type you want, collect them in an ASG and have the task slicing scale the ASG accordingly.
Right now - you have to manually determine the slice size for each container-to-EC2 and manually scale the ASG.
Further, it was noted that ECS is actually NOT AZ aware and it will spread load over EC2 instances in the pool -- but it wont also balance the tasks across AZs....
So, its a fantastic version one... but these are some resiliency and scaling features that should have already been included.
When I'm balancing a single deployment across multiple AZs (e.g. US-East -> US-West), the latencies between the containers seem far higher than just the 200-300ms predicted by speed of light. Am I doing something wrong?
Thanks again - this is really helpful. I had talked to someone who had left Amazon but knew the internal workings who said ECS was Mesos just privately branded like Chef -> OpsWorks, but I guess I must have misunderstood.
I've been using IBM Container Service. They have Docker containers running on bare metal servers with a free tier and a trial account for 30 days. With respect to clusters, you can set up a scalable group with min/max sizes and they'll take care of routing across the containers in the group.
I was once let go from a company for "just not being a good fit" after landing them a successful contract with bigTechCo here in the bay area and earning them over $1mm in services.
Further, they had showed me that my bonus was going to be over $27K one three separate occasions, then they let me go before having to pay me the bonus because I had to be actually employed there to receive my share of the money earned from me doing 100% of the work.
People should not be able to be fired for "not being a good fit" they should have concrete documented issues on which to fire someone.