AutospotManagedServices

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:

• [1] https://ci.apache.org/projects/flink/flink-docs-release-1.5/internals/stream_checkpointing.html
• [2] https://ci.apache.org/projects/flink/flink-docs-release-1.5/internals/job_scheduling.html
• [3] https://medium.com/netflix-techblog/can-spark-streaming-survive-chaos-monkey-b66482c4924a
• [4] https://aws.amazon.com/blogs/aws/aws-batch-run-batch-computing-jobs-on-aws/