In our continuing series on Designing Techniques For Building Stateful Cloud-Native Applications (see Part 1 and Part 2), we now take a look at how messaging types, Event Sourcing, and CQRS apply to cloud-native design.

Lightbend today announced the general availability of Lightbend Pipelines, a new, comprehensive system that accelerates all lifecycle aspects of streaming data pipelines and integrating them with microservices-based applications.

The Lagom team and contributors are proud to announce the release of Lagom 1.5.0!

Akka 2.5.0 was released 2 years ago, and since then we have released 22 patch releases. This means that it's high time for a new minor release...

After much testing and intense development of a few important features, we are confident that Akka Typed has the quality and performance to be used in production.

We’re pleased to announce a new release of Lightbend Telemetry, part of Lightbend Platform.

Convert 10 minutes into a charity donation!

In Part 1 of our series on Design Techniques For Building Stateful, Cloud-Native Applications, we looked at the topics of Resiliency, Recoverability, and Scalability for cloud-native applications like Reactive Microservices and real-time streaming systems. In this part, we take a look at application state, and why we should distribute it. Let’s start with defining the word state.

In this Ask Lightbend Anything blog series, my colleague Alexander Golubyev, Senior Consultant at Lightbend, compiled a list of the most frequently asked questions from our conversations with hundreds of enterprises.

In this webinar with Lightbend's Craig Blitz, Product Director, and Kiki Carter, Principal Enterprise Architect, we review how Lightbend’s Pipelines module enables you to develop components ("streamlets") using the appropriate technology, wire them together as pipelines, and deploy them with Kubernetes without all the manual, time-consuming labor.

For a long time, stateless services have been the primary choice for developers. While on the surface building a stateless web app or microservice may be the right way to go, in some cases it is not necessarily the best approach for cloud-native services.

Our partners at IBM have created a brand new series for developers titled "Reactive in practice: A complete guide to event-driven systems development in Java".

Welcome to this technical series on getting long-term value from Machine Learning (ML) with Kubeflow on Lightbend Platform with Red Hat OpenShift.

In Part 1 of this series “How To Deploy And Use Kubeflow On Red Hat OpenShift”, we discussed what Kubeflow is, and how it can be useful for running Machine Learning applications in production. In this post, we discuss installation of Kubeflow.

In Part 2 of “How To Deploy And Use Kubeflow On OpenShift”, we looked at Installation and some of the additional components used by Kubeflow, such as Ambassador, Spartakus, Argo, Minio, etc. In this post, we will describe and show how to use some of them.

In Part 3 of “How To Deploy And Use Kubeflow On OpenShift”, we looked at Kubeflow support components like Argo, Ambassador, Minio, and Spartakus. In this post, we look at using JupyterHub.

In Part 4 of “How To Deploy And Use Kubeflow On OpenShift”, we looked at setting up and using JupyterHub with Kubeflow. In this post, we look closer at running Machine Learning jobs with TensorFlow.

In Part 5 of “How To Deploy And Use Kubeflow On OpenShift”, we looked at machine learning in production. In this part, we turn our attention to tuning ML parameters with Kubeflow and Katib.

In Part 6 of “How To Deploy And Use Kubeflow On OpenShift”, we examined Kubeflow ML parameters tuning. In this part, we look at serving ML models in production.

In Part 7 of “How To Deploy And Use Kubeflow On OpenShift”, we looked at model serving with Kubeflow. In this part, we now look at deploying Kubeflow pipelines.