In our latest article on the Amazon Builders’ Library, Yan Cui highlights the main takeaways from the article, Implementing health checks, by AWS Principal Engineer David Yanacek.

Azure Functions is a serverless compute service that lets you run event-triggered code without having to explicitly provision or manage infrastructure, in other words, Microsoft’s Azure Functions is a modern serverless architecture, offering event-driven cloud computing that is easy for developers to use. This blog is about Azure Functions triggers and bindings.

App containerization has picked up momentum in recent years as it helps to save costs, time and resources. Resource vendors are available to assist in containerization of one or two apps, but most vendors struggle to execute a large number of app containerization projects with the same skill level and outcomes. As a matter of fact, it’s a manual approach in certain scenarios with a lot of dependencies which is not only time and cost consuming but also prone to errors and miscalculations.

AWS has a lot of services, and they all generate logs. A lot of logs. We’ve worked hard to make sure you can capture logs from every source and service on AWS, and today we’re happy to announce the final piece of our AWS logging puzzle: LogDNA’s S3 Collector integration. It’s an easy-to-use Lambda function that lets you ingest any AWS logs that get dumped to S3 – like logs from CloudFront and ELB.

Logs from a variety of different AWS services can be stored in S3 buckets, like S3 server access logs, ELB access logs, CloudWatch logs, and VPC flow logs. S3 server access logs, for example, provide detailed records for the requests that are made to a bucket. This is very useful information, but unfortunately, AWS creates multiple .txt files for multiple operations, making it difficult to see exactly what operations are recorded in the log files without opening every single .txt file separately.

Serverless development opens lots of new opportunities, and if you’re invested in serverless (or you’ve been following the hype) you’ll know that cost efficiency is principal among those benefits. Simply put, we can save money by choosing the right tool for the right task. Since a distributed microservices architecture is made up of many managed services it’s a simple task to change out the building blocks of a particular application flow.

Local prototyping has become de rigueur for most web stack developers in the last few years. Even complex web backends are generally assumed to be emulatable from a developer’s laptop. But this assumption breaks down a bit as we explore the AWS platform in general. More specifically, serverless architecture challenges the system of local prototyping.

It is no secret that it is not that hard to accidentally spend a boatload of money on AWS. This Twitter user told the story of his $77,000 mistake with a monkey emoji (because what’s funnier than spending the price of an entry level Tesla by accident.) The scary part is that many of us have been there. If you are not looking at your cloud bill every day, it is easy to let the costs run up quickly, then suffer from bill shock when it arrives a month later.

You may know my series of blog posts about BizTalk Server Tips and Tricks that I normally write in the BizTalk360 blog. Well, the goal of this Logic Apps Tips and Tricks series will be the same; to provide simple tips or tricks that may improve your performance on developing Logic Apps workflows, avoiding issues, apply best practices and so on. But you may think, “What a strange way to start this topic, deprecated actions? Why should I use deprecated actions?”.

Sysdig, an industry leader for monitoring and security of cloud-native workloads, and IBM have joined forces to bring a fully Integrated powerful platform that delivers the security and performance that enterprises need in today’s multi-cloud world. Sysdig Secure and the IBM Cloud Pak for Multicloud Management (MCM) can help you accelerate Kubernetes and cloud adoption by addressing security and regulatory compliance from the start on enterprise hybrid cloud environments.