-
Notifications
You must be signed in to change notification settings - Fork 4
MM Blog article #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MM Blog article #28
Conversation
article.md
Outdated
* What if it would be able to trigger different type of events? | ||
* Can it be detached from FINP architecture? | ||
|
||
It was how LambdaCron was worn. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*born
@sean-garvey, @nickagel, @vincetse, Open to hear suggestions to improve the article: things to include or remove. |
@fsargent , |
article.md
Outdated
@@ -109,6 +109,6 @@ The job is scheduled to run at 5 pm on the 5th every month. The **type** of the | |||
|
|||
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. | |||
|
|||
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. | |||
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maintenance*
article.md
Outdated
@@ -14,7 +14,7 @@ The most simple and straightforward way to schedule task is using Linux [crontab | |||
|
|||
### 2. AWS CloudWatch Events | |||
|
|||
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: | |||
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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a negative change.
You don't need ",service which is"
Preakness should have two 's' to be consistent with the rest of the article.
Revert this change.
@fsargent , fixed. |
No description provided.