Downloaded 54 times
![How does a function look like
function.json
"bindings": [
{
"type": "httpTrigger",
"direction": "in",
"webHookType": "genericJson",
"name": "req"
},
{
"type": "http",
"direction": "out",
"name": "res"
},
{
"type": "queue",
"name": "eventOutput",
"queueName": "aievents1",
"connection":"AiStorageConnection",
"direction": "out"
}
]
public static class OrderHandler
{
[FunctionName("OrderWebhook")]
public static async Task<HttpResponseMessage> Run(
[HttpTrigger] HttpRequestMessage req,
[Queue("aievents1", Connection = "AiStorageConnection")]
IAsyncCollector<String> eventOutput,
TraceWriter log)
{
log.Info($"Webhook was triggered!");
string jsonContent = await req.Content.ReadAsStringAsync();
dynamic data = JsonConvert.DeserializeObject(jsonContent);
await eventOutput.AddAsync(
JsonConvert.SerializeObject(GetLogData(data)));
int orderId = PlaceOrder(data);
return req.CreateResponse(HttpStatusCode.OK,
new {orderNumber = orderId });
}
. . .
}](https://image.slidesharecdn.com/hur252wrtintwncwiybc-signature-00761efefc3d85775d2a48026556d9e9718c9a3d27a0702b56a7a7f037d1fc36-poli-170526084310/75/DevOps-in-the-era-of-serverless-computing-Alessandro-Vozza-Codemotion-Amsterdam-2017-31-2048.jpg)
Uploaded byCodemotion
DevOps in the era of serverless computing - Alessandro Vozza - Codemotion Amsterdam 2017
The document discusses the concept of serverless computing, highlighting its benefits such as reduced time to market and scalability, along with the characteristics of serverless architectures. It addresses common misconceptions and challenges associated with serverless, including costs and ecosystem lock-in. Additionally, it focuses on the evolution of DevOps practices in the context of serverless technology and offers resources for further exploration.
More Related Content
Similar to DevOps in the era of serverless computing - Alessandro Vozza - Codemotion Amsterdam 2017
DevOps in the era of serverless computing - Alessandro Vozza - Codemotion Amsterdam 2017
- 1. DevOps in aServerless world Alessandro Vozza, Technical Evangelist, Microsoft AMSTERDAM 16 - 17 MAY 2017
- 2. All you needis code Alessandro Vozza, Technical Evangelist, Microsoft AMSTERDAM 16 - 17 MAY 2017
- 3. Look mom, noservers! Alessandro Vozza, Technical Evangelist, Microsoft AMSTERDAM 16 - 17 MAY 2017
- 4. The disappearance ofservers David Copperfield, Magician AMSTERDAM 16 - 17 MAY 2017
- 5. Better DevOps thruServerless Alessandro Vozza, Technical Evangelist, Microsoft AMSTERDAM 16 - 17 MAY 2017 Title making
- 6. HELLO! I am Alessandro Iam here because I love technology. You can find me at @bongo Feedback: https://aka.ms/talkfeedback
- 7. 1. What the heckis serverless Let’s start with some basics
- 8. The Evolution ofApplication Platforms
- 9.
- 10.
- 11.
- 12. POST Users Users/Id Users/Id Users/Id CreatUser GetUser UpdateUser DeleteUser GET UPDATE DELETE Client Mang. DB Microservices Serverless Container? OS Patch? ServerSize/ Scale? Application’s architecture over time
- 13.
- 14.
- 17. »Higher-order, abstracted deliverymodel for code »Scalable outsourced runtime-as-a-service »Nano- and femto-services »The tech is there, but needs refinement »”Enterprise” Serverless? So what is it again?
- 18. What is “serverless” Event- drivenscale Sub-second billing Abstraction of servers
- 19. Benefits of “serverless” Manage less Micro-pricingEase of scale
- 21.
- 22.
- 23. The Dark sideof Serverless
- 24. »Is not PaaS »Isnot NoOps »Is not limitless »Is not lock-in free What Serverless is NOT:
- 25. The myth ofNoOps
- 26. Serverless is notfree Cost API calls Complexity ~400.000
- 27. »Cold start »Ecosystem lock-in »Longrunning processes »Security? Serverless Pitfalls
- 28. 2. Serverless deep dive Up& close to functions
- 29.
- 30. wwwroot | - host.json |- proxies.json | - mynodefunction | | - function.json | | - index.js | | - node_modules | | | - ... packages ... | | - package.json | - mycsharpfunction | | - function.json | | - run.csx Folder Structure
- 31. How does afunction look like function.json "bindings": [ { "type": "httpTrigger", "direction": "in", "webHookType": "genericJson", "name": "req" }, { "type": "http", "direction": "out", "name": "res" }, { "type": "queue", "name": "eventOutput", "queueName": "aievents1", "connection":"AiStorageConnection", "direction": "out" } ] public static class OrderHandler { [FunctionName("OrderWebhook")] public static async Task<HttpResponseMessage> Run( [HttpTrigger] HttpRequestMessage req, [Queue("aievents1", Connection = "AiStorageConnection")] IAsyncCollector<String> eventOutput, TraceWriter log) { log.Info($"Webhook was triggered!"); string jsonContent = await req.Content.ReadAsStringAsync(); dynamic data = JsonConvert.DeserializeObject(jsonContent); await eventOutput.AddAsync( JsonConvert.SerializeObject(GetLogData(data))); int orderId = PlaceOrder(data); return req.CreateResponse(HttpStatusCode.OK, new {orderNumber = orderId }); } . . . }
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38. Serverless Apps Lifecycle Design DevelopDeploy Monitor Serverless apps lifecycle
- 39. Design Design Develop DeployMonitor Serverless design
- 40. Serverless Architecture /orderprocessing O365 App Insights /index.html Azure FunctionsProxies /couponprocessing
- 41. Develop Design Develop DeployMonitor Development cycle
- 42.
- 43. Design Develop DeployMonitor Deployment options
- 44. Deployment process Production StageChris-Dev Push (automatic) Manual sync
- 45. Monitor Design Develop DeployMonitor Monitoring serverless apps
- 46. Key Scenarios forMonitoring Monitor Learn Optimize Alert
- 47. Do I needcloud?
- 48. 3. How will itaffect DevOps If at all
- 49. The Evolution ofDevOps
- 50. #DEVOPS #YOLO DevOps ischanging
- 51.
- 53. 5. What next? To thecloud and beyond
- 54. https://aka.ms/azafr »Serverless remote codeexecution »Applications are cloud + edge »Data and events stream »Seamless access Edge and distributed computing http://searchdatacenter.techtarget.com/definition/edge-computing
- 55. 5. Conclusion Is it forme? How to get started?
- 56.
- 57.
- 58.
- 59.
- 60. THANKS! Any questions? You canfind me at » @bongo » [email protected] Credits: slides template from SlidesCarnival