<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Shift Left Consultants blog</title>
    <link>https://shiftleftconsultants.com/blog</link>
    <description>Java, Spring Boot and Quarkus on AWS: measured results and what they cost.</description>
    <language>en</language>
    <item>
      <title>Migrating Spring Boot to Quarkus: what a working port doesn't tell you</title>
      <link>https://shiftleftconsultants.com/blog/migrate-spring-boot-to-quarkus</link>
      <guid isPermaLink="true">https://shiftleftconsultants.com/blog/migrate-spring-boot-to-quarkus</guid>
      <pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate>
      <description>Porting Spring Boot to Quarkus is now the quick part. Five questions a passing test suite can't answer, and the cold-start numbers for deciding whether to move.</description>
      <category>java</category>
      <category>spring-boot</category>
      <category>quarkus</category>
      <category>migration</category>
      <category>graalvm</category>
      <category>aws-lambda</category>
    </item>
    <item>
      <title>Your Spring Boot migration compiles. Will it survive the first traffic spike?</title>
      <link>https://shiftleftconsultants.com/blog/spring-boot-migration-traffic-spike</link>
      <guid isPermaLink="true">https://shiftleftconsultants.com/blog/spring-boot-migration-traffic-spike</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
      <description>We sent 200 simultaneous cold requests to an AI-generated Quarkus migration on AWS Lambda. The generated version handled 2. After two changes, 68. Then the database ceiling showed up.</description>
      <category>java</category>
      <category>aws-lambda</category>
      <category>spring-boot</category>
      <category>quarkus</category>
      <category>migration</category>
      <category>rds-proxy</category>
      <category>snapstart</category>
    </item>
    <item>
      <title>We ran one Spring Boot app on Lambda five ways. The defaults were the problem</title>
      <link>https://shiftleftconsultants.com/blog/tuning-spring-boot-and-quarkus-on-lambda</link>
      <guid isPermaLink="true">https://shiftleftconsultants.com/blog/tuning-spring-boot-and-quarkus-on-lambda</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate>
      <description>Five ways to run one Spring Boot app on AWS Lambda, measured. Tuning took SnapStart from 3.5 s to 1.2 s, and one Hibernate default cost Spring 30 ms a request.</description>
      <category>java</category>
      <category>aws-lambda</category>
      <category>spring-boot</category>
      <category>quarkus</category>
      <category>snapstart</category>
      <category>graalvm</category>
      <category>hibernate</category>
    </item>
    <item>
      <title>Why we run Java on AWS Lambda instead of Python or Go</title>
      <link>https://shiftleftconsultants.com/blog/why-java-on-lambda-not-python-or-go</link>
      <guid isPermaLink="true">https://shiftleftconsultants.com/blog/why-java-on-lambda-not-python-or-go</guid>
      <pubDate>Sat, 10 Oct 2026 00:00:00 GMT</pubDate>
      <description>The usual advice says Java starts too slowly for Lambda. We run 17 Java functions anyway: measured cold starts, a 51,000-request load test, and what it cost us.</description>
      <category>java</category>
      <category>aws-lambda</category>
      <category>quarkus</category>
      <category>graalvm</category>
      <category>spring-boot</category>
    </item>
  </channel>
</rss>
