Geen Kindle-apparaat vereist. Download een van de gratis Kindle-apps om Kindle-boeken te lezen op je smartphone, tablet en computer.
Als je de gratis app wilt ontvangen, moet je je mobiele telefoonnummer invoeren.
AWS Step Functions: Developer Guide (English Edition) Kindle-editie
Alle indelingen en edities bekijken Andere indelingen en edities verbergen
|Lengte: 633 pagina's||Taal: Engels|
Deze winkelfunctie blijft items laden wanneer de Enter-toets wordt ingedrukt. Als je deze carrousel wilt verlaten, gebruik je je sneltoets om naar de volgende of vorige kop te bladeren.
Klanten die dit item hebben gekocht, kochten ook
Pagina 1 van 1 Opnieuw beginnenPagina 1 van 1
This is official Amazon Web Services (AWS) documentation for Amazon Step Functions. AWS Step Functions makes it easy to coordinate the components of distributed applications as a series of steps in a visual workflow. You can quickly build and run state machines to execute the steps of your application in a reliable and scalable fashion. This documentation is offered here as a free Kindle book, or you can read it online or in PDF format at https://docs.aws.amazon.com/step-functions/.
Nog geen klantenrecensies
|5 sterren (0%)||0%|
|4 sterren (0%)||0%|
|3 sterren (0%)||0%|
|2 sterren (0%)||0%|
|1 ster (0%)||0%|
Nuttigste klantenrecensies op Amazon.com
Amazon.com: 1 recensies
Great guide to an incredibly valuable service!24 augustus 2018 - Gepubliceerd op Amazon.com
I spent many hours in the office during the Summer of 2017 writing AWS Lambda function to create a serverless service for Bloomberg "Per Security" data requests. This guide was a great help. It clearly described how to return custom error codes from AWS Lambda functions, as well as how to handle errors. One of the challenges my team and I faces when writing code to retrieve data from data services is that many of these services need to use sftp. Often these servers would get tied up waiting for data, or would try and fail. Cron is limited. And my experience is that any long running process on a server will eventually fail as a result of the accumulated entropy of opening network connections, threads waiting. And cron brings the added joy of deploying code and managing cron tabs. Clearly a cloud scale service is more reliable as a scheduler. And when combined with AWS Lambda functions each time the function is triggered it only knows the JSON you inject into it--which makes it much easier to repeat an invocation using step functions. When a step function executed you can always recreate this because it logs the exact data it passed to your function. Step functions serve almost like a trellis, a supporting structure that will uplift your code and help you to simplify what each function does by preserving state, but also providing for a well understood interface. By using this guide, plus a lot of time coding we were able to simplify a data retrieval process to a combination of CloudWatch Events, Step Functions, and AWS Lambda functions and to manage encryption keys with AWS Secrets Manager (an upgrade from our initial process that used S3 KMS encryption and AWS Lambda environment variable encryption. What you will find in this guide is clear information that you can apply to replace legacy schedulers. I could not believe the $2MM license fee I saw for one firms license of a legacy scheduler. But the real cost savings with step functions is that processes can be broken down, code can be simplified, and your team can focus on building new services rather than wrestling with file and batch scheduling. One group we've worked with has three full time staff just managing file retrieval and ingestion. Take this guide and you can see incredible improvements in how you code, manage, and process data.
Een iemand vond dit nuttig