Microservices

Burr Sutter (@burrsutter) and I (@christianposta) have finished writing a small book to help folks get up and running with Istio.io service mesh! Download the complimentary e-book at developers.redhat.com.

This is part eight of a ten-week series and covers using the Canary Deployment pattern to ease code into production. Istio makes this easy while giving you several good options for intelligent routing. And you can do it all without changing your source code.

From Idea to Deployment the Agile Way--Part II: The whole API lifecycle should go agile in order to stay relevant. But, this is made difficult because new service-based architectures make dependencies skyrocket. It’s time to think of a new way to deliver APIs--mocking and testing included--to simplify and accelerate the process of shipping production-ready APIs.

In the last post, we saw how Eclipse Vert.x can interact with a database. To tame the asynchronous nature of Vert.x, we used Future objects. In this post, we are going to see another way to manage asynchronous code: reactive programming. We will see how Vert.x combined with Reactive eXtensions gives you superpowers.

Discover how using Istio with OpenShift and Kubernetes eases microservices production and deployment. (Part 7 of 10 in a series)

Introducing OpenShift.io, an open online development environment for planning, creating and deploying hybrid cloud services.

Tutorials and training on how to build secure applications using the latest in

In this post, we will deploy the existing Coolstore microservices demo as a service mesh and start to demonstrate the tangible value you can get out of the system without any major rewrite or rearchitecture of the existing app. We'll also improve our project along the way to adhere to Istio best practices.

The whole API lifecycle should go agile in order to stay relevant. But, this is made difficult because new Service-Based Architecture makes dependencies skyrocket! It’s time to think of a new way to deliver APIs - mocking and testing included - to simplify and accelerate the process of shipping production ready APIs.

Testing software is challenging and very important. Testing for correctness is one thing, but testing for failures in network reliability is quite another task. This article will demonstrate how Istio makes this oh so easy.

In this post we are going to see how we can use JDBC in an Eclipse Vert.x application, and this, using the asynchronous API provided by the vertx-jdbc-client.

distributed architectures introduce more complexity, services meshes can help soften the landing and shift some of that complexity out of our applications and place it where it belongs, in the application operational layer: Bringing Coolstore Microservices to the Service Mesh: Part 1 - Exploring auto-injection

In this article, we will discuss using the Apache Camel-ZooKeeper component, and how we can set up a fail-over scenario for Apache Camel routes. While working in a clustered environment, situations arise where a user wants to have a backup route which will become active only when the master route stops working.

Istio brings tracing and monitoring to your system with very little effort, helping you keep things humming. This article covers Istio Tracing & Monitoring: Where are you are and how fast are you going?

This post is part of the Introduction to Eclipse Vert.x series. In the last post, we saw how this application became configurable and how we can use a random port in a test. Let’s go a bit further this time and develop a CRUD-ish / REST-ish application.

The phrase "Failure is not an option" is tossed about with much bravado, with Istio Circuit Breaker. But the fact remains, things eventually fail. Everything. How, then, do you handle the inevitable failure of your microservices? This article will show you how.

In this post, we are going to enhance our Eclipse Vert.x application we created in the previous post to support external configuration, and then show how to deal with different configuration sources.

This is week three of a ten-week series about Istio, kubernetes and OpenShift. The series started with an introduction to Istio, and this week covers Istio Circuit Breaker: How To Handle (Pool) Ejection.

This Vert.x crash class will present how you can develop a simple application using Vert.x, how to test it, package it and run it. So you have a great start on the road to building an amazing system on top of Vert.x.

This article covers Istio Route Rules and telling Service Requests Where To Go. OpenShift and Kubernetes do a great job of working to make sure calls to your microservice are routed to the correct pods. What if, however, you want to customize the routing?

Today Red Hat is making Node.js generally available to Red Hat customers through a subscription to Red Hat OpenShift Application Runtimes (RHOAR).

This article will describe the main features of the MicroProfile Fault Tolerance specification and then demonstrate how it was implemented in WildFly Swarm, the Red Hat MicroProfile implementation.

Following is a diverse set of developer-related breakouts, workshops, BoFs, and labs for Red Hat Summit 2018. With these 61+ sessions, we believe that every attending application developer will come away with a strong understanding of where Red Hat is headed in this app dev space.

this is an introduction to Istio. Istio helps automate the developer time to implement a feature. The combination of code complexity and code heft (i.e. number of lines of code) can put a drag on an implementation. Istio is a better way.

This article shows how developers writing Java-based microservices can leverage the Eclipse Microprofile 1.2 specifications for Configuration and Health checks to take advantage of the management capabilities provided by Red Hat OpenShift and Kubernetes.