diff --git a/index.xml b/index.xml index 84e9bd128..31bdbb7e5 100644 --- a/index.xml +++ b/index.xml @@ -263,7 +263,7 @@ down into a few broad areas:</p>Corehttp4k Corehttps://http4k.org/ecosystem/http4k/Mon, 01 Jan 0001 00:00:00 +0000https://http4k.org/ecosystem/http4k/Your first http4k apphttps://http4k.org/tutorial/your_first_http4k_app/Mon, 01 Jan 0001 00:00:00 +0000https://http4k.org/tutorial/your_first_http4k_app/<p>Welcome to the world of http4k! In this guide, we&rsquo;ll run you through the steps required to get up and running with your first Kotlin server application. We&rsquo;ll generate the project, make some requests to it and then build it into a runnable application. By the end, you&rsquo;ll have a fully working app built packaged and tested using the Gradle build tool.</p>http4k Connecthttps://http4k.org/ecosystem/connect/Mon, 01 Jan 0001 00:00:00 +0000https://http4k.org/ecosystem/connect/Serverless http4k with AWS Lambdahttps://http4k.org/tutorial/serverless_http4k_with_aws_lambda/Mon, 01 Jan 0001 00:00:00 +0000https://http4k.org/tutorial/serverless_http4k_with_aws_lambda/<p>In this guide, we&rsquo;ll run you through the steps required to get an http4k application deployed and running on AWS Lambda and available to call over the internet using AWS ApiGateway. If you&rsquo;re not familiar with the http4k concepts for HTTP and Serverless apps, then we advise you read them <a href="https://http4k.org/ecosystem/http4k/concepts/http/">here</a> and <a href="https://http4k.org/ecosystem/http4k/concepts/serverless/">here</a>. To make an app you can follow the <a href="https://http4k.org/tutorial/your_first_http4k_app/">Your first http4k app</a> tutorial before tackling this guide.</p>Going native with Graal on AWS Lambdahttps://http4k.org/tutorial/going_native_with_graal_on_aws_lambda/Mon, 01 Jan 0001 00:00:00 +0000https://http4k.org/tutorial/going_native_with_graal_on_aws_lambda/<p>In this guide, we&rsquo;ll run you through the steps required to get an http4k application deployed and running on AWS Lambda with GraalVM and available to call over the internet using AWS ApiGateway. If you&rsquo;re not familiar with the http4k concepts for HTTP and Serverless apps, then we advise you read them <a href="https://http4k.org/ecosystem/http4k/concepts/http/">here</a> and <a href="https://http4k.org/ecosystem/http4k/concepts/serverless/">here</a>. To make an app you can follow the <a href="https://http4k.org/tutorial/your_first_http4k_app/">Your first http4k app</a> tutorial. Then follow the steps in the <a href="https://http4k.org/tutorial/serverless_http4k_with_aws_lambda/">Serverless http4k with AWS Lambda</a> tutorial before tackling this guide.</p>CVE-2024-55875: XXE(XML External Entity Injection) vulnerabilityhttps://http4k.org/security/cve-2024-12345/Thu, 12 Dec 2024 00:00:00 +0000https://http4k.org/security/cve-2024-12345/<h3 id="description">Description</h3> <p>There is a XXE(XML External Entity Injection) vulnerability when http4k handling malicious XML contents within requests, which might allow attackers to read local sensitive information on server, trigger Server-side Request Forgery and even -execute code under some circumstances.</p>http4k v6 and beyond! Introducing Enterprise Edition and Long-Term Supporthttps://http4k.org/news/http4k-v6-and-ee/Tue, 03 Dec 2024 00:00:00 +0000https://http4k.org/news/http4k-v6-and-ee/<h4 id="tldr">TL;DR</h4> +execute code under some circumstances.</p>Preview: http4k v6 and beyond! Introducing Enterprise Edition and Long-Term Supporthttps://http4k.org/news/http4k-v6-and-ee/Tue, 03 Dec 2024 00:00:00 +0000https://http4k.org/news/http4k-v6-and-ee/<h4 id="tldr">TL;DR</h4> <ul> <li>http4k will release its next major version (6) in January 2025</li> <li>http4k Community Edition (CE) - will continue to be released under the existing Apache 2 license.</li> diff --git a/news/http4k-v6-and-ee/index.html b/news/http4k-v6-and-ee/index.html index 84214b79f..58589fc3e 100644 --- a/news/http4k-v6-and-ee/index.html +++ b/news/http4k-v6-and-ee/index.html @@ -1,5 +1,5 @@ -http4k v6 and beyond! Introducing Enterprise Edition and Long-Term Support | http4k -

http4k v6 and beyond! Introducing Enterprise Edition and Long-Term Support

December 2024 / the http4k team

TL;DR

  • http4k will release its next major version (6) in January 2025
  • http4k Community Edition (CE) - will continue to be released under the existing Apache 2 license.
  • From v6, http4k CE will set its minimum supported target JVM version to 21.
  • We are introducing the http4k Enterprise Edition (EE) subscription under a new commercial license, which will provide LTS support for http4k v5 and older JVMs as well as enterprise support features.

A brief history of time

From its inception over seven years ago, http4k has been increasingly adopted by teams looking to leverage its powerful simplicity, focus on testability and uncompromised stability in their projects. That now translates to over two million monthly downloads. With over 150 modules, http4k has continued to grow steadily and to have some of the most flexible support and integrations available in the Kotlin ecosystem, all backed up by rock-solid test suites and our trademark lightweight approach.

As the JVM and Kotlin ecosystems evolve, we’re committed to taking advantage of the latest features of the underlying platforms, while continuing to provide the best level of support for teams working on all versions.

With that in mind, we’re very excited to announce that the next major version of the http4k ecosystem (all 150+ modules of it!) will be released in January 2025. This release marks the start of a new chapter for the project and as usual we will be taking the opportunity to make some strategic breaking changes to the core of the library, removing all those annoying deprecations, and do some more general tidying on the entire codebase as groundwork for the future. We will also be renaming some modules to make things a bit more consistent.

We will of course, document all of these changes and provide a simple migration guide.

Into the future

From the beginning of the project, the http4k team have strived to support the widest array of environments that we could, and have continued to support JVM versions 8 and above for all http4k releases, avoiding backward incompatibilities wherever possible. However, we always knew that this decision could not last indefinitely and we are taking this opportunity to move forward into the future in a more strategic way. As well as learning from our mistakes and making some changes to the core of the library, this will allow us to take advantage of newer JVM features and optimisations in the target class file format which should provide a performance boost for all users.

From http4k v6, major versions of the open source http4k ecosystem - now taking on the name http4k Community Edition (CE) - will be released to be aligned with the regular support cadence of the underlying Long Term Support (LTS) JVM versions from Oracle. As such, http4k CE version 6 will set its minimum Java version to 21 (which Oracle will provide public updates until late 2026) for a period of 24 months until the aligned major Community version is released in January 2027.

To put that more visually, this is the timeline for current and future Java LTS releases:

What does that mean for me?

For teams adopting the non-legacy versions of Java and http4k, nothing changes. The development of http4k as a primarily open-source solution means teams can count on the existing release cadence of http4k CE (averaging to once a week) and active community support by the toolkit creators in the Kotlin Slack (you can join via this link).

In addition, we’re officially introducing an LTS support option for http4k v5 through the http4k Enterprise Edition (EE) subscription, to be released under the new commercial http4k Enterprise License, to provide peace of mind to companies who are unable to move to the most recent Java versions but still want to ensure stability and security in their http4k applications.

Based on the above Java timeline, the plan is for future major http4k versions to have the following Community and Enterprise Edition (LTS) update schedule:

The launch feature set for http4k EE will consist of:

  • up to 24 months of LTS support for http4k ecosystem v5, including access to both source and binary versions of the libraries, which will be accessed through private GitHub and Maven repositories. Security patches and essential bug fixes will be proactively released as required.
  • Access to priority support channels (via email and dedicated http4k Slack instance) for direct support access to http4k expertise.
  • Full licence reporting for all http4k modules.
  • Discounted consultancy and training rates delivered by core contributors to the http4k ecosystem.

In future, subscribers to http4k EE will also automatically gain access to planned http4k Pro features and integrations as they become available which will provide further advantages to teams. These expert-designed, proprietary extensions will reflect real-world requirements and enterprise patterns built from years of successfully delivering complex systems with http4k. Watch this space!

The aim of http4k EE is to provide a level of support to major releases of the toolkit through a commercial offering and strengthen the investment in the evolution of the http4k ecosystem as a whole.

If your company is interested in longer-term access to http4k version 5 or want to take advantage of the peace-of-mind benefits provided by http4k EE, please get in touch with the team to arrange a call, either by reaching out on the Kotlin Slack instance or through our email channels at enterprise@http4k.org. You can also read more about the offering on the http4k Enterprise Edition page.

In the meantime, the team will be busy paving the way for the next chapter in the whole http4k ecosystem. Please join us in the Kotlin Slack to discuss the upcoming changes and to provide feedback on the roadmap,

Get ready for version 6 in January!

/Peace out

Team http4k