Changelog History
Page 3
-
v1.5.1 Changes
May 03, 2019π These releases bring into Lagom a new
Service Locatorimplementation, based on Akka's Service Discovery. This component was previously released as an apart library, lagom-akka-discovery-service-locator, and intended to be a replacement for the Service Locator previously offered by Lightbend Orchestration.π For more information, consult the corresponding documentation for Akka Discovery integration:
- π Java API Lagom 1.5
- π Scala API Lagom 1.5
π For a list of the specific changes in Lagom 1.5.1, see the change log (1.5.1).
Credits
Thanks to the community for their detailed bug reports and contributions.
π Thanks to Lightbend for their continued sponsorship of the Lagom core teamβs efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Steve Swing, Ignasi Marimon-Clos, Dale Wijnand, Tim Moore, Alden Torres.
-
v1.5.0 Changes
April 16, 2019π We are happy to announce the availability of Lagom 1.5.0. This is the GA release of Lagom 1.5.0 and is production ready. We invite all our users to upgrade.
π This version builds on top of the 2.7.x series of Play, Alpakka Kafka 1.0, and the latest improvements on Akka and Akka Management. See GitHub for the full list of commits.
Hereβs a list of the most relevant improvements.
Akka Management
π Akka Management is a suite of tools for operating Akka powered applications. Akka Management uses a dedicated HTTP port to expose a few routes allowing remote inspection of the state of the Akka Actor System. For example, if the process is a member of an Akka Cluster, these endpoints will report if the node already joined the cluster.
0οΈβ£ Lagom exposes the Akka Management HTTP port out of the box. Lagom will add Health Check routes by default. You can reuse library provided health checks or plugin your own. For example, Lagom uses cluster status to determine when the node is healthy. This is called Cluster Membership Check and is provided by the Akka Cluster HTTP Management library.
π Another improvement Lagom 1.5 introduces, thanks to the adoption of Akka Management, is the simpler, more robust cluster formation via Akka Cluster Bootstrap. Instead of using a static list of seed nodes or relying on convoluted custom scripts to build the list of seed nodes dynamically, Cluster Bootstrap discovers the existing nodes via plugins adapting Akka Cluster Bootstrap to your orchestration environment (e.g. Kubernetes, Marathon). A static list of seed nodes is still supported but we recommend migrating to Cluster Bootstrap.
π Deployment with Kubernetes or Red Hat OpenShift
π Lagom 1.5.0 will no longer support Lightbend Orchestration (which was Incubating). Despite accelerating the first deployment, using Lightbend Orchestration was producing friction and reducing flexibility to tune the deployment. Moving forward, there will be no automated handling of the deployment and the suggested way is to manually maintain the production settings, the deployment descriptors and related scripts.
π If you are targeting OpenShift or Kubernetes environments the new Guide to Deploy Lightbend Applications covers all the steps and details (including a sample application) to set up and tune your system.
Akka gRPC integration
π Lagom 1.5.0 introduces incubating support for Akka gRPC for cross-service communication. The original HTTP/JSON-based transport is not disappearing but, instead, Lagom introduces gRPC so users can choose to expose alternative transports increasing the adoption of their services.
This feature drove some smaller improvements which non-gRPC users will also welcome.
π Lagom already supported HTTP/2 since it is built on top of Play. In Lagom 1.5 weβve reviewed all the necessary pieces so HTTP/2 can also be used on dev mode. In the same spirit, it is now also possible to use encrypted (TLS) communication on dev mode.π As a final improvement driven by the adoption of gRPC, Lagom 1.5 now supports Additional Routers (Java API / Scala API), which lets you embed any vanilla Play Router into a Lagom service. You are now able to easily reuse the Play and Akka building blocks whenever the Lagom API is not enough to complete the task at hand. Using Additional Routers it is trivial to reuse Play code you already had or extend Lagom with low-level features supported in Play but not exposed in Lagom directly (such as uploading files).
π Couchbase Persistence Support
π Lagom 1.5 also offers optional support for Couchbase as a new database option for persistent entities and read side processors through the Akka Persistence Couchbase module. Currently available in an Incubating early access release, Akka Persistence Couchbase has been built to work with Lagom 1.5 and the 1.0 release is coming soon. See the documentation for Couchbase Persistent Entities and Couchbase Read-Side support for more details.
Migrating from previous versions
π This release introduces very little changes over the
1.5.0-RC2so if you already moved to that version the upgrade should be trivial. If you are still using Lagom1.4.xwe recommend you first migrate to the latest version available of Lagom 1.4 series and then migrate to Lagom 1.5. If you are using a version older than1.4.x, you should migrate one version at a time. For example: from1.3.9to1.3.11(because1.3.11is1.3.latest), then from1.3.11to1.4.latestand finally to1.5.x. Read the appropriate release notes and migration guides (Java / Scala) on each step.Credits
Thanks to the community for their detailed bug reports and contributions.
π Thanks to Lightbend for their continued sponsorship of the Lagom core teamβs efforts. Lightbend offers commercial support for Lagom.
π Special thanks to the following contributors who helped with this release:
commits author 53 Ignasi Marimon-Clos 37 Renato Cavalcanti 20 Tim Moore 16 Dale Wijnand 15 Elijah Rippeth 11 Marcos Pereira 4 Martynas MickeviΔius 3 Ayush Prashar 2 Alden Torres 1 sullis 1 danielklein45 1 Zhonglai Zhang 1 Sergey Morgunov 1 Riccardo Sirigu 1 Prashant Sharma 1 Piyush Goyal 1 Kunal sethi 1 JoΓ£o Guitana 1 Ido Shamun 1 Enno 1 Corey Auger 1 Brent Eritou 1 0xflotus -
v1.4.15 Changes
August 22, 2019π The Play Team is pleased to announce the release of Lagom Framework 1.4.15. This is the latest stable release of Lagom 1.4.x series.
π Lagom 1.4.15 includes a backport of #2161 to fix a problem that appears when running tasks across multiple Scala versions, for example,
sbt +publishLocal. There are also minor internal changes and documentation fixes. For a list of the specific changes in Lagom 1.4.15 see the change log (1.4.15).Credits
Thanks to the community for their detailed bug reports and contributions.
π Thanks to Lightbend for their continued sponsorship of the Play core teamβs efforts. Lightbend offers commercial support for Lagom.
-
v1.4.14 Changes
May 17, 2019π The Play Team is pleased to announce the release of Lagom Framework 1.4.14. This is the latest stable release of Lagom 1.4.x series.
Lagom 1.4.14 includes a backport of #1773. Special thanks to @ihostage for the fix.
π For a list of the specific changes in Lagom 1.4.14 see the change log (1.4.14).
Credits
Thanks to the community for their detailed bug reports and contributions.
π Thanks to Lightbend for their continued sponsorship of the Play core teamβs efforts. Lightbend offers commercial support for Lagom.
-
v1.4.13 Changes
May 15, 2019π The Play Team is pleased to announce the release of Lagom Framework 1.4.13. This is the latest stable release of Lagom 1.4.x series.
π Lagom 1.4.13 brings in Play 2.6.23 and a new version of play-ws (v1.1.13) that includes an important bug fix on streamed calls. In case of an error, after a connection is established, the error is now properly propagated. See playframework/play-ws#340
π For a list of the specific changes in Lagom 1.4.13 see the change log (1.4.13).
Credits
Thanks to the community for their detailed bug reports and contributions.
π Thanks to Lightbend for their continued sponsorship of the Play core teamβs efforts. Lightbend offers commercial support for Lagom.
-
v1.4.13-a5bd71c7
May 10, 2019 -
v1.4.12 Changes
May 03, 2019π These releases bring into Lagom a new
Service Locatorimplementation, based on Akka's Service Discovery. This component was previously released as an apart library, lagom-akka-discovery-service-locator, and intended to be a replacement for the Service Locator previously offered by Lightbend Orchestration.In order to allow a smoother transition for Lagom 1.4 users, we decided to include it in 1.4.12. So users can choose to first migrate their Lagom 1.4 application to Akka Service Discovery and then to Lagom 1.5. Of course, this is not a required step. It is also possible to migrate directly from Lagom 1.4 and Lightbend Orchestration to Lagom 1.5 and Akka Service Discovery.
π For more information, consult the corresponding documentation for Akka Discovery integration:
- π Java API Lagom 1.4
- π Scala API Lagom 1.4
π For a list of the specific changes in Lagom 1.4.12 see the change log (1.4.12).
Credits
Thanks to the community for their detailed bug reports and contributions.
π Thanks to Lightbend for their continued sponsorship of the Lagom core teamβs efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Steve Swing, Ignasi Marimon-Clos, Dale Wijnand, Tim Moore, Alden Torres.