4 ms·
While I think this is a cool idea, I'm really not sure how it works after reading through the features page and the landing page. I can't tell which resources i
by nostrebored 6y ago
While I think this is a cool idea, I'm really not sure how it works after reading through the features page and the landing page. I can't tell which resources it spins up and down. The listed supported components like DynamoDB and S3 seem like strange choices here -- I'm guessing S3 shifts objects to Glacier and restores them and DynamoDB changes provisioned capacity, but I've walked away with more questions than answers.
If anyone here is on the team, can you provide a bit more details as to what's happening behind the scenes?
Maybe I am misunderstanding the product and it's really an orchestration tool around when an environment is spun up and down, but then I'm having a hard time seeing the benefit over CloudWatch Events -> Lambda -> Pipeline.
I discuss issues like this with customers regularly, and I'd really love to be able to introduce this into conversations, but I need a bit more to go on :)
- helsinkiandrew 6y agoI'm a little confused on what it does exactly too - is it a 'better' cloudformation with timed launch/termination and cost estimation?
- radedespodovski 6y agoHi, I am Rade from Microtica. The benefit of Microtica Cost Optimizer over using CloudWatch+Lambda comes when you have to manage more different schedules. With CloudWatch+Lambda solution you also have to manage the schedule infrastructure no matter how simple that infrastructure is, this could become an overwhelming repetitive task. We added additional features like: 1. automated resource tagging 2. enable/disable schedule 3. manual start/stop of resources assigned to a particular scheduler 4. cost and saving dashboard 5. notifications Cost Optimizer is just one feature of the Microtica product. Microtica is a DevOps automation tool that you can use to provision complete cloud infrastructure and deliver applications on Kubernetes using CI/CD. The components you are referring are ready peaces of infrastructure that you can just pick up, combine and provision in the cloud. Behind the scenes, we register a schedule in our system and when start/stop event is fired, first we obtain temporary credentials (assume role) for the AWS account where resources to be scheduled reside, then we call AWS APIs to perform scheduling operations over EC2 and RDS.
- nostrebored 6y agoThanks for the explanation!