March 2024 Summaries

AWS has introduced LLRT (Low Latency Runtime), an experimental JavaScript runtime designed to optimize serverless applications on AWS Lambda by significantly reducing cold start times and lowering costs. Unlike general-purpose runtimes like Node.js, LLRT focuses on serverless efficiency, utilizing Rust for a smaller executable size and QuickJS for a lightweight JavaScript engine, resulting in 10x faster startups and 2x lower costs according to AWS benchmarks. However, LLRT's design, which excludes JIT compilation, makes it less suitable for compute-intensive tasks and some API functionalities, positioning it as a specialized tool for serverless environments rather than a direct replacement for Node.js. While LLRT aims to improve Lambda's cost-effectiveness compared to alternatives like Cloudflare Workers, it remains experimental and not recommended for production workloads.

Vantage has introduced a new feature allowing users to apply custom discounts to imported Databricks costs, addressing the discrepancy between list prices and actual negotiated rates for enterprise customers. This update enables users to input their specific discount rates on Databricks SKU groups within the Vantage UI, ensuring that cost reports accurately reflect the true costs being paid to Databricks. The process involves selecting the desired integration, entering the discount percentage for each SKU group, and saving these inputs, which triggers the reprocessing of billing data and subsequent update of cost reports. The feature, which is free for all users, currently supports various AWS SKU groups but does not include the AWS Security and Compliance SKU group. Users must have owner permissions to set these discounts, and the integration is currently supported only for AWS.

Usage attribution in Datadog offers organizations detailed insights into their spending by utilizing tagging strategies to optimize resource allocation and cost management. By implementing consistent tagging schemas, organizations can streamline cost allocation and facilitate informed decision-making. Tags, which are key/value pairs, help organize resources and can be used for cost allocation by associating expenses with specific resources or departments. The usage attribution feature allows users to assign up to three tag keys to monitoring data, providing fine-grained insights into resource utilization and associated costs, although it is an Enterprise feature requiring support activation. This capability enables organizations to analyze costs by tags such as environment, team, or application, facilitating better budget allocation and resource optimization. Additionally, tools like Vantage can integrate with Datadog to offer cross-provider usage analysis, enhancing visibility and helping organizations manage their cloud infrastructure costs more effectively.

Amazon Aurora and Neon are both serverless Postgres services that offer unique pricing models and features, suitable for different use cases. Aurora, integrated within the AWS ecosystem, provides regular updates, global availability, and seamless integration with AWS services like Lambda and S3, with pricing based on Aurora Capacity Units (ACUs) that cannot scale to zero. Neon, a newer entrant, offers true serverless capabilities with the ability to scale to zero, branching features for development environments, and open-source transparency. In various scenarios, Neon's pricing proved to be more cost-effective than Aurora's due to its idle-time savings, although Aurora was less expensive in situations where compute was consistently utilized. Aurora's I/O-Optimized option and Neon's competitive pricing for I/O-intensive applications make both platforms appealing, though Neon's ability to not charge for idle time often results in lower costs.

Distributed SQL query engines like Trino and Amazon Athena enhance the ability to run fast, interactive queries on large data sets but can significantly increase costs on storage systems like Amazon S3 due to high volumes of GET requests. While Athena's straightforward pricing structure includes charges per terabyte of data scanned, the additional costs from S3 requests can surpass storage expenses, especially when querying numerous objects. The underlying issue lies in data storage not being optimized with processing methods, which Apache Iceberg can address by improving the Hive table format to support updates and deletes, reducing the number of objects and GET requests. Implementing caching strategies with technologies such as Amazon CloudFront or ElastiCache can further mitigate costs by minimizing repetitive requests, although these strategies can be complex when dealing with unpredictable query patterns. For example, Starburst's Warp Speed dynamically updates caches based on workload patterns, significantly reducing costs and improving query performance. Overall, while Trino represents a new generation of powerful query engines, newer technologies like Iceberg and strategic caching can optimize cost-efficiency and performance in data analytics workflows.

Vantage has announced the integration of Coralogix into its platform, enabling users to view Coralogix costs alongside those from other infrastructure providers within the Vantage console. This integration allows customers to gain a comprehensive understanding of their cloud expenses by visualizing usage-based costs for logs, metrics, traces, and security events through the Coralogix Data Usage Service API. By connecting Vantage to a Coralogix organization using an API key, users can access detailed cost data categorized by services, subsystems, and applications. This development aims to address the challenge of fragmented cost visibility across multiple providers, facilitating more informed decisions regarding resource allocation and optimization strategies. The feature is accessible to all Vantage users at no additional cost, with daily data refreshes and support for multiple Coralogix teams. Additionally, Vantage plans to expand its support to other providers like fly.io, ClickHouse, and Vercel.

Vantage has introduced a new API endpoint that allows users to manage and import business metrics, facilitating the automation of creating and ingesting these metrics into their platform. This development enables users to assign imported metrics to Cost Reports to visualize unit costs, such as Cost per Daily Active User, thereby eliminating the previous manual process of uploading CSV files. The new /business_metrics endpoint allows users to create, update, and delete business metrics, with the ability to automate data imports daily. This feature caters to users with time-series data in non-integrated systems and is available at no extra cost. Users can leverage this API to better understand and manage their cloud costs by visualizing business metrics alongside cost data, providing clearer insights into unit costs and enhancing data accuracy.

Vantage has expanded its payment options by allowing customers to subscribe to its Enterprise Tier plans through the Azure Marketplace, providing a convenient and secure method for Azure users to facilitate payments to Vantage using their existing Azure billing details. Previously, customers could only pay through ACH, credit card via Stripe, or the AWS Marketplace, which posed additional management tasks for Azure-centric organizations. By subscribing through the Azure Marketplace, Azure acts as a payment intermediary without sharing billing details with Vantage, simplifying the process for customers who use Azure as their primary cloud provider. Transitioning to this new payment method does not affect current credit card subscribers unless they choose to switch, and while coupons are not currently supported, no additional fees are incurred. Custom pricing is available, though self-serve plans are not supported, and only fixed-term contracts are offered through this payment channel.

The blog post discusses the integration of FinOps as Code principles with Terraform to automate the creation of a cost reporting structure in Vantage, a cloud cost optimization tool. By leveraging Infrastructure as Code practices, organizations can visualize their cloud costs alongside their business structure, improving cost management and alignment with business objectives. The post provides a detailed demonstration of setting up an organization structure using a structured YAML file to map business units and cost centers, and iteratively creating corresponding resources in Vantage, including folders, cost reports, and dashboards. This approach allows for tailored reporting that meets the diverse needs of stakeholders, from management to engineers, while enhancing the efficiency of resource management and cost tracking. The tutorial assumes an intermediate understanding of Terraform and requires setting up a Vantage API token, enabling users to quickly deploy and manage cost-reporting resources suitable for their organizational units.

Vantage has introduced a new feature that allows users to group resources by tagged status in Cost Reports and cost allocation segments, enabling a comprehensive view of their tagging structure. This functionality helps users quickly determine which resources are tagged or not, facilitating improved cost allocation insights without any additional cost. The tagged grouping dimension is available in the console, API, and Terraform, making it accessible to all customers. This enhancement simplifies the process of analyzing resource tagging at a high level, ensuring customers can efficiently track and optimize their cloud costs.

Vantage has introduced a new feature that allows users to add saved filters to dashboards, enabling consistent filtering across all Cost Reports within a dashboard. This enhancement eliminates the previous need for duplicating dashboards and individually adding filters for different teams, thereby streamlining the reporting process. Users can define filter criteria once and apply them across multiple reports, with the option to use "AND" or "OR" logic between existing and saved filters based on the provider used. This feature, available at no additional cost, currently applies only to Cost Reports but plans are underway to expand its use to segment reports. Future integration with the API and Terraform is also anticipated.