The next online DevNation Live Tech Talk will be Thursday, May 17th at 12 p.m. EDT. The topic is " Serverless and Servicefull Applications: Where Microservices Complements Serverless" presented by Burr Sutter.
You're in an IT department. How does the rest of the organization see you? As a valuable asset whose code and APIs make a difference in the marketplace, or as a necessary evil that should be trimmed wherever possible? Containers, microservices, and serverless computing can get you where you need to go.
The past nine weeks of blog posts have introduced, explained, and demonstrated some of the many features of the Istio service mesh when combined it is with Red Hat OpenShift and Kubernetes. This, the final post in this series, is a recap.
The Eclipse MicroProfile project is moving fast with four releases and eight subspecs having at least two implementations each. This post provides an overview of MicroProfile 1.3, which was released on September 30th, and helps you to get started with the specification.
It’s been an incredibly exciting journey for Eclipse Che since the acquisition of Codenvy by Red Hat. Che 6 is the most important release in Eclipse Che history—it is a big release with more than 1,550 commits. So there’s a ton of new goodness for everyone!
Using Istio with Red Hat OpenShift and Kubernetes makes life with microservices easier. But what if you want your microservice to talk to another service that is outside of your OpenShift/Kubernetes/pods environment? Enter Istio Egress.
From Idea to Deployment the Agile Way--Part III: 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.
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.
Discover how using Istio with OpenShift and Kubernetes eases microservices production and deployment. (Part 7 of 10 in a series)
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 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 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).
Build here. Go anywhere.
We serve the builders. The problem solvers who create careers with code.
Join us if you’re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.