<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
      <title>Jess&#39;s Blog</title>
      <link>https://blog.jessizen.com</link>
      <description>Software engineer at AWS; Engineer in Residence at the Rust Foundation</description>
      <generator>Zola</generator>
      <language>en</language>
      <atom:link href="https://blog.jessizen.com/rss.xml" rel="self" type="application/rss+xml"/>
      <lastBuildDate>Thu, 27 Aug 2026 00:00:00 +0000</lastBuildDate>
      <item>
          <title>Engineer in Residence at the Rust Foundation</title>
          <pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate>
          <author>Jess Izen</author>
          <link>https://blog.jessizen.com/posts/engineer-in-residence-rust-foundation/</link>
          <guid>https://blog.jessizen.com/posts/engineer-in-residence-rust-foundation/</guid>
          <description xml:base="https://blog.jessizen.com/posts/engineer-in-residence-rust-foundation/">&lt;p&gt;&lt;em&gt;This was pulled from my old &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/posts/jess-izen-12085b161_i-am-excited-to-put-on-an-additional-hat-activity-7498790203780943872-6Pr0&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I am excited to put on an additional hat: Engineer in Residence at the Rust Foundation, seconded for a year by AWS.&lt;/p&gt;
&lt;p&gt;Rust is in a moment of great opportunity, and I believe that the Rust community can chart a new course for the industry in supply chain security and maintainer sustainability. I&#39;m looking forward to getting my hands dirty working full-time on infrastructure and programs that reach all Rust users.&lt;/p&gt;
&lt;p&gt;Besides the colleagues I mentioned in the &lt;a rel=&quot;external&quot; href=&quot;https://rustfoundation.org/media/welcoming-jess-izen-as-engineer-in-residence-at-the-rust-foundation/&quot;&gt;linked post&lt;/a&gt; from the Rust Foundation, Rust Project, Rust community, and AWS, I want to give a special thank you to open source leaders that have shared a steady stream of advice about how companies like AWS can fit into this story while supporting maintainer autonomy: &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/josh-aas-406a772/&quot;&gt;Josh Aas&lt;/a&gt;, &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/benjamuk/&quot;&gt;Benjamin Nickolls&lt;/a&gt;, &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/flamefew/&quot;&gt;Henri Yandell&lt;/a&gt;, &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/alexscammon/&quot;&gt;Alexander Scammon&lt;/a&gt;, &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/georgechellapa/&quot;&gt;George Chellapa Ph.D.&lt;/a&gt;, &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/duaneobrien/&quot;&gt;Duane O&#39;Brien&lt;/a&gt;, &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/aevaonline/&quot;&gt;Æva Black&lt;/a&gt;.&lt;/p&gt;
</description>
      </item>
      <item>
          <title>Funding Rust through the Rust Commercial Network</title>
          <pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate>
          <author>Jess Izen</author>
          <link>https://blog.jessizen.com/posts/funding-rust-commercial-network/</link>
          <guid>https://blog.jessizen.com/posts/funding-rust-commercial-network/</guid>
          <description xml:base="https://blog.jessizen.com/posts/funding-rust-commercial-network/">&lt;p&gt;&lt;em&gt;This was pulled from my old &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/posts/jess-izen-12085b161_rust-commercial-network-activity-7477800063289749504-11nP&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Does your company depend on Rust?&lt;/p&gt;
&lt;p&gt;Join industry peers in funding OSS maintainers and development time for the Rust ecosystem and toolchain. We are pooling funds for both basic maintenance and directed work towards areas affecting our businesses.&lt;/p&gt;
&lt;p&gt;You can see open funding opportunities in the &lt;a rel=&quot;external&quot; href=&quot;https://rust-commercial-network.github.io/rcn/funding-directory.html&quot;&gt;RCN funding directory&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/predrag-gruevski-0abb36296/&quot;&gt;Predrag Gruevski&lt;/a&gt; and I are launching this new funding initiative through the &lt;a rel=&quot;external&quot; href=&quot;https://rustfoundation.org/rust-commercial-network/&quot;&gt;Rust Commercial Network (RCN)&lt;/a&gt;, part of the &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/company/rust-foundation/&quot;&gt;Rust Foundation&lt;/a&gt;. Membership is not required to participate.&lt;/p&gt;
&lt;p&gt;Small and large contributions are welcome. If you want to help seed the project, we’re preparing a launch announcement with the initial projects funded, participating companies, and total amount raised. Founding partners include &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/company/amazon-web-services/&quot;&gt;Amazon Web Services (AWS)&lt;/a&gt;, &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/company/openai-dev/&quot;&gt;OpenAI for Developers&lt;/a&gt;, and &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/company/arm/&quot;&gt;Arm&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Predrag and I are holding office hours starting next week, July 8 at 8am US/Pacific. We can help you route an OSS budget, pitch a budget to your leadership, or figure out logistics for Rust OSS work you have in mind.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://lnkd.in/g7FEuVfz&quot;&gt;Come to office hours or discuss async&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Update: These office hours are no longer running.&lt;/em&gt;&lt;/p&gt;
</description>
      </item>
      <item>
          <title>Wide events and metrique 0.1.24</title>
          <pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate>
          <author>Jess Izen</author>
          <link>https://blog.jessizen.com/posts/wide-events-metrique-0-1-24/</link>
          <guid>https://blog.jessizen.com/posts/wide-events-metrique-0-1-24/</guid>
          <description xml:base="https://blog.jessizen.com/posts/wide-events-metrique-0-1-24/">&lt;p&gt;&lt;em&gt;This was pulled from my old &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/posts/jess-izen-12085b161_release-metrique-v0124-awslabsmetrique-activity-7449895340465393664-kyQk&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;There&#39;s been a lot of interest in flight recording lately, such as &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/russell-cohen-b75b9927/&quot;&gt;Russell Cohen&lt;/a&gt; and my &lt;a rel=&quot;external&quot; href=&quot;https://github.com/dial9-rs/dial9&quot;&gt;dial9 tokio flight recorder&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;But, metrics are still very useful! After all, you need a metric to go red or a dashboard to look weird, in order to know to analyze traces in the first place. In particular, I prefer wide events, which lets you emit simple metrics, but also preserve high-cardinality metadata for drill downs or aggregating for trends. The workflow I use is, metric to alert/dashboard, wide event queries to contextualize, trace to deep dive.&lt;/p&gt;
&lt;p&gt;In support of this, I maintain a wide-events-as-metrics library, &lt;a rel=&quot;external&quot; href=&quot;https://github.com/awslabs/metrique&quot;&gt;metrique&lt;/a&gt;, which is the main Rust metrics library used inside Amazon. The TLDR is that it lets you use macros to tag structs with metrics, which do the &quot;right thing&quot; on drop, very cheaply, with embedded measurements and metadata. Its API is very async-friendly: you can fan out to child tasks that fold data back into your main emission, and delay flushing (but not foreground flow) until all segments finish. Currently EMF, JSON, and custom formats are supported, OTLP coming soon.&lt;/p&gt;
&lt;p&gt;Our latest release, &lt;a rel=&quot;external&quot; href=&quot;https://github.com/awslabs/metrique/releases/tag/metrique-v0.1.24&quot;&gt;0.1.24&lt;/a&gt;, brings a few nice features:&lt;/p&gt;
&lt;p&gt;We now have a turnkey integration with &lt;a rel=&quot;external&quot; href=&quot;https://github.com/tokio-rs/tokio-metrics&quot;&gt;tokio-metrics&lt;/a&gt; (which I also maintain), that allows automatically emitting tokio runtime metrics as metrique records. We already had a similar integration for &lt;a rel=&quot;external&quot; href=&quot;https://metrics.rs/&quot;&gt;metrics.rs&lt;/a&gt; aggregated metrics. But, with metrique, we are setting ourselves up to fold &quot;what was the state of the tokio runtime during this request&quot; into wide event records, which is neat. Kudos to &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/joulei/&quot;&gt;Julian Montes de Oca&lt;/a&gt; for this feature.&lt;/p&gt;
&lt;p&gt;Second, we now support emitting &quot;properties&quot; (metadata strings) as &lt;code&gt;[&quot;arrays&quot;, &quot;of&quot;, [&quot;possibly&quot;, &quot;nested&quot;], &quot;strings&quot;]&lt;/code&gt;. AWS Cloudwatch Log Insights and most other backends gracefully handles complex properties in EMF (or JSON) records, but AFAIK, few off the shelf EMF libraries do. I&#39;ve frequently found myself manually casting properties to &lt;code&gt;&quot;list,of,values&quot;&lt;/code&gt;, so this should be a nice paper cut fix.&lt;/p&gt;
&lt;p&gt;Finally, I added support for &lt;code&gt;Counter::increment_owned&lt;/code&gt;, which adds tokio friendly bounds to its guard. It lets you bump up a global counter that captures eg current requests in flight for one wide event, and decrement the counter after the request ends.&lt;/p&gt;
&lt;p&gt;We will be tabling at &lt;a rel=&quot;external&quot; href=&quot;https://www.tokioconf.com/2026&quot;&gt;TokioConf&lt;/a&gt; next week, come find us!&lt;/p&gt;
</description>
      </item>
      <item>
          <title>Lambda Rust Runtime 1.1.1</title>
          <pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate>
          <author>Jess Izen</author>
          <link>https://blog.jessizen.com/posts/lambda-rust-runtime-1-1-1/</link>
          <guid>https://blog.jessizen.com/posts/lambda-rust-runtime-1-1-1/</guid>
          <description xml:base="https://blog.jessizen.com/posts/lambda-rust-runtime-1-1-1/">&lt;p&gt;&lt;em&gt;This was pulled from my old &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/posts/jess-izen-12085b161_release-v111-awsaws-lambda-rust-runtime-activity-7438296402595651584-wDwN&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The Lambda Rust Runtime just published our first big release post-1.x.&lt;/p&gt;
&lt;p&gt;The headline new feature is concurrent invocation processing on a single lambda instance, using tokio&lt;sup class=&quot;footnote-reference&quot;&gt;&lt;a href=&quot;#tokioconf&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;. We have an open issue about &lt;a rel=&quot;external&quot; href=&quot;https://github.com/aws/aws-lambda-rust-runtime/issues/1120&quot;&gt;adding further runtime options here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This was a tricky release to plan for. We knew we wanted to improve ergonomics, since we had to lock down a lot of previously wide-open types for 1.0. Over the years, we had gotten comfortable releasing a rapid-fire stream of breaking &lt;code&gt;lambda-events&lt;/code&gt; versions to keep up with AWS record changes. (Sure was nice while it lasted)&lt;/p&gt;
&lt;p&gt;The new builders for event types were a good compromise, since we had to tag our previously public event types as &lt;code&gt;#[non_exhaustive]&lt;/code&gt; for 1.0. &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/lucianomammino/&quot;&gt;Luciano Mammino&lt;/a&gt; added some custom builders for SQS &amp;amp; Kinesis to keep stream processing nice. And then, &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/astraeaqs/&quot;&gt;Astraea S.&lt;/a&gt; added a generalized builder for all other events (&lt;a rel=&quot;external&quot; href=&quot;https://bon-rs.com/&quot;&gt;bon&lt;/a&gt; under the hood).&lt;/p&gt;
&lt;p&gt;I also like what we did with the extension API&#39;s telemetry records. They are now optionally generic, which lets you deserialize directly into json (or a fancier type) with no intermediate parsing. This brings the ergonomics closer to managing a regular invocation event handler. (That was a slog of a PR, thanks &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/raphaeltheriault/&quot;&gt;Raphaël Thériault&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;Kudos and appreciation to &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/davide-melfi/&quot;&gt;Davide Melfi&lt;/a&gt; for leading the release!&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://github.com/aws/aws-lambda-rust-runtime/releases/tag/lambda_runtime-v1.1.1&quot;&gt;Release notes&lt;/a&gt;&lt;/p&gt;
&lt;div class=&quot;footnote-definition&quot; id=&quot;tokioconf&quot;&gt;&lt;sup class=&quot;footnote-definition-label&quot;&gt;1&lt;/sup&gt;
&lt;p&gt;Come to &lt;a rel=&quot;external&quot; href=&quot;https://www.tokioconf.com/2026&quot;&gt;TokioConf&lt;/a&gt; in Portland, 4/20-4/23.&lt;/p&gt;
&lt;/div&gt;
</description>
      </item>
      <item>
          <title>AWS Lambda officially supports Rust</title>
          <pubDate>Fri, 14 Nov 2025 00:00:00 +0000</pubDate>
          <author>Jess Izen</author>
          <link>https://blog.jessizen.com/posts/aws-lambda-officially-supports-rust/</link>
          <guid>https://blog.jessizen.com/posts/aws-lambda-officially-supports-rust/</guid>
          <description xml:base="https://blog.jessizen.com/posts/aws-lambda-officially-supports-rust/">&lt;p&gt;&lt;em&gt;This was pulled from my old &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/posts/jess-izen-12085b161_release-release-10-awsaws-lambda-rust-runtime-activity-7395174562159763459-izHZ&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Starting today, AWS Lambda functions officially support Rust!&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://aws.amazon.com/blogs/compute/building-serverless-applications-with-rust-on-aws-lambda/&quot;&gt;Release blog&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;You can install the supporting runtime via &lt;a rel=&quot;external&quot; href=&quot;https://crates.io/crates/lambda_runtime&quot;&gt;crates.io&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I am a maintainer of the Rust lambda runtime. It&#39;s exciting to see what started as a scrappy, community-driven project reach official status. This comes with SLAs and roadmap support that will give developers confidence to build in Rust on Lambda.&lt;/p&gt;
&lt;p&gt;Excited to see what new ideas &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/astraeaqs/&quot;&gt;Astraea Quinn S.&lt;/a&gt; and the Lambda team bring to the open source project!&lt;/p&gt;
&lt;p&gt;And, credit to &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/david-calavera/&quot;&gt;David Calavera&lt;/a&gt; for founding the project, and thank you to champions like &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/lucianomammino/&quot;&gt;Luciano Mammino&lt;/a&gt; and &lt;a rel=&quot;external&quot; href=&quot;https://www.linkedin.com/in/james-eastham/&quot;&gt;James Eastham&lt;/a&gt; for helping the runtime achieve industry adoption.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://github.com/aws/aws-lambda-rust-runtime/releases/tag/v1.0&quot;&gt;Runtime 1.0 release notes&lt;/a&gt;&lt;/p&gt;
</description>
      </item>
    </channel>
</rss>
