Whats the point: AWS extends savings to Lambda, Azure drills on costs, Travis goes large, OAS goes 3.0.3

What's the point

AWS has extended its Compute Savings Plans to cover Lambda functions, promising savings of up to 17 per cent. The vendor’s Savings Plans apply to customers making a one or three year commitment to consuming a defined amount of specified EC2 or AWS Fargate capacity. AWS’s Cost Explorer tool will now take Lambda into account when recommending Savings Plans to customers.

Azure drills down on costs

Microsoft has given its Azure costing tools a bit of a do over, adding new resource drilldowns in the resource view under cost analysis. The vendor said the cost by resource view has been improved to help users better understand the costs they’re accruing for each resource at a meter level, along with its associated services. Users can also manage each resource from cost analysis by clicking on the resource in the cost by resource view.

Travis CI goes large on instances

Travis CI has announced that it will support larger instance types on travis-ci.com, so that users can “leverage the additional computing power to also incorporate more elaborate testing scenarios in your testing workflow”. The CI vendor said this would deliver “more performant builds”, to match the needs of developers in areas such as machine learning, AI and big data, amongst others, which demand more resources during development, testing and production.

OpenAPI Initiative opens up v3.0.3

The OpenAPI Initiative has released v3.0.3 of the OpenAPI Specification. The OpenAPI Spec aims to define “a standard, programming language-agnostic interface description for REST APIs, which allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic.” The latest rev aims to “improve the specification in terms of readability and accuracy”, and doesn’t introduce any changes in the behaviour of the spec.