WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

AutospotManagedServices

Jump to bottom Edit New page
lenucksi edited this page Jul 20, 2018 · 3 revisions

Rationale

This page collects information on usability of Autospotting for AWS managed services as detailed in https://github.com/cristim/autospotting/issues/281 .

Requirements

There are a number of requirements limiting the feasibility and value of this approach, some of which are listed below. The bold parts represent the matching table column.

  • ASG A service needs to be realized using an ASG to be handled
    • ASG-ACCESS The ASG needs to be accessible
  • HANDLES_FAILURE A service needs to be able to handle sudden infrastructure failure and replacement.
    • The service needs to run long enough such that an instance replacement is worthwhile.
    • The cost of instance replacement in terms of potentially needed reprocessing of data needs to outweigh what is gained by replacing it.

Table

Service ASG ASG-ACCESS HANDLES_FAILURE Known Usage References
EMR Flink ? ? Possible - [1,2]
EMR Spark ? ? Possible - [3]
Batch ? ? Possible - [4]
BeanStalk Y Y ? - @cristim
...add me

References:

Add a custom footer
Add a custom sidebar

Clone this wiki locally