You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: article.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ The most simple and straightforward way to schedule task is using Linux [crontab
14
14
15
15
### 2. AWS CloudWatch Events
16
16
17
-
AWS configures events using [CloudWatch](http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/WhatIsCloudWatchEvents.html), to invoke other AWS services in a cron-like way. As the team's infrastructure is based on AWS, using AWS services to schedule events made total sense. Preakness also uses Simple Queue Service (SQS) to queue jobs integrated with CloudWatch events. It seemed like a good option, however we found some negative aspects we didn't feel comfortable with:
17
+
AWS configures events using [CloudWatch](http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/WhatIsCloudWatchEvents.html), to invoke other AWS services in a cron-like way. As the team's infrastructure is based on AWS, using AWS services to schedule events made total sense. Preaknes uses Simple Queue Service (SQS) to queue jobs, service which is integrated with CloudWatch events. It seemed like a good option, however we found some negative aspects we didn't feel comfortable with:
18
18
19
19
* The service itself has some serious [limitations](http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/cloudwatch_limits_cwe.html)
20
20
* Events are attached to AWS services and depend on AWS releases.
@@ -37,7 +37,7 @@ That was how LambdaCron was born.
37
37
38
38
LambdaCron is a serverless cron tool. It provides an easy way to run scheduled tasks on the AWS cloud, defined in YAML, managed by a command line tool and using the same syntax for expressions as Linux [crontab](https://help.ubuntu.com/community/CronHowto). LambdaCron fills in the gap by providing a way to manage Serverless cron jobs just like cron. With LambdaCron you define each of your tasks in an independent YAML file.
39
39
40
-
LambdaCron offers 4 different types of tasks:
40
+
LambdaCron offers 5 different types of tasks:
41
41
42
42
***Queue task**: send a message to AWS SQS queue.
43
43
***Lambda task**: invoke AWS Lambda function.
@@ -49,9 +49,9 @@ It is integrated with 4 AWS services and HTTP requests. LamdaCron is easily inte
49
49
50
50
The tool is production ready but it still has a long way to go. It satisfies the needs of MediaMath's Financial Platform but there is room to increase functionality and improve. The three main lines where we feel it must improve are:
51
51
52
-
* Tasks: cover all options in the current type of tasks and continue adding new types.
53
-
* CLI: improve and continue adding functionality to the CLI so tasks can be totally managed from the command line and without login in the AWS console.
54
-
* Templates: use a templating system to define tasks and be able to include variables in the definition.
52
+
***Tasks**: cover all options in current type of tasks and continue adding new types.
53
+
***CLI**: improve and continue adding functionality to the CLI. Tasks should be totally managed from the command line and without login in the AWS console.
54
+
***Templates**: use a templating system to define tasks and be able to include variables in the definition.
55
55
56
56
## Use Case
57
57
@@ -109,6 +109,6 @@ The job is scheduled to run at 5 pm on the 5th every month. The **type** of the
109
109
110
110
Before creating tasks, a LambdaCron environment must be deployed by following the instructions in the [README](https://github.com/mediaMath/lambda-cron) of the project.
111
111
112
-
LambdaCron CLI also provides commands that can automate tasks. E.G. validate and upload tasks to a LambdaCron environment using Continuous Integration tools. We will follow up with more examples and how to work with LambdaCron in future blog posts.
112
+
LambdaCron CLI also provides commands that can automate development and maintenace tasks. E.G. validate and upload tasks to a LambdaCron environment using Continuous Integration tools. We will follow up with more examples and how to work with LambdaCron in future blog posts.
113
113
114
114
Any service accessible by an API (including non AWS services) can be reached by LambdaCron so you don't have to rely on additional services features to schedule your tasks and/or write extra code.
0 commit comments