15 changed files with 158 additions and 1 deletions
@ -0,0 +1,11 @@ |
|||||
|
--- |
||||
|
title: "Webinar: Develop. Deploy. Deliver continuously." |
||||
|
date: 2019-10-10T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
On the 10th October 2019, I spoke at a Red Hat webinar on a session named _"Simplify your API Strategy with Istio"_ where I showcased the integration between 3scale and Istio. |
||||
|
|
||||
|
For more information: https://www.redhat.com/en/events/webinar/develop-deploy-deliver-continuously |
||||
|
|
||||
|
{{< youtube 4kiKuqbI9QM >}} |
||||
@ -0,0 +1,10 @@ |
|||||
|
--- |
||||
|
title: "Red Hat Forum Helsinki 2019" |
||||
|
date: 2019-10-08T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
On the 08th October 2019, I spoke at Red Hat Forum Helsinki on a session named |
||||
|
_"Agile Integration: Transforming Enterprises - Nothing happens until something is integrated"_. |
||||
|
|
||||
|
For more information: https://events.redhat.com/profile/form/index.cfm?PKformID=0x65475abcd |
||||
@ -0,0 +1,11 @@ |
|||||
|
--- |
||||
|
title: "Red Hat Summit 2019" |
||||
|
date: 2019-05-08T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
On the 8th May 2018, I spoke at Red Hat Summit on three sessions named: |
||||
|
|
||||
|
- _"Leverage the power of communities to manage your APIs"_ ([demo recording](https://www.youtube.com/watch?v=IaNOypl00o8)) |
||||
|
- _"Istio, the missing link in the evolution of your API strategy"_ ([demo recording](https://www.youtube.com/watch?v=kLTQNGslgB4)) |
||||
|
- _"An APIcast policy in 15 minutes"_ ([demo recording](https://www.youtube.com/watch?v=q1RJBW2N-Xg)) |
||||
@ -0,0 +1,14 @@ |
|||||
|
--- |
||||
|
title: "Red Hat Tech Exchange 2019" |
||||
|
date: 2019-10-21T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
During the three Red Hat Tech Exchange sessions (Americas, EMEA and APAC), I presented two sessions: |
||||
|
|
||||
|
- _"Leverage the power of open source communities to manage your APIs"_ ([full recording](https://youtu.be/I2QutGqIzpA)) |
||||
|
- _"Complementing your Istio Service Mesh with 3scale and Fuse"_ ([demo recording](https://www.youtube.com/watch?v=Wvrnzc7b9qw)) |
||||
|
|
||||
|
The session _Leverage the power of open source communities to manage your APIs_ has been the second best voted session in RHTE APAC! |
||||
|
|
||||
|
 |
||||
@ -0,0 +1,11 @@ |
|||||
|
--- |
||||
|
title: "3scale toolbox: Deploy an API from the CLI" |
||||
|
date: 2019-07-29T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
Deploying your API from a CI/CD pipeline can be a tremendous amount of work. The latest release of Red Hat Integration greatly improved this situation by adding new capabilities to the 3scale CLI. The 3scale CLI is named 3scale toolbox and strives to help API administrators to operate their services as well as automate the delivery of their API through Continuous Delivery pipelines. |
||||
|
|
||||
|
Having a standard CLI is a great advantage for our customers since they can use it in the CI/CD solution of their choice (Jenkins, GitLab CI, Ansible, Tekton, etc.). It is also a means for Red Hat to capture customer needs as much as possible and offer the same feature set to all our customers. |
||||
|
|
||||
|
[Continue reading](https://developers.redhat.com/blog/2019/07/29/3scale-toolbox-deploy-an-api-from-the-cli/) |
||||
@ -0,0 +1,16 @@ |
|||||
|
--- |
||||
|
title: "5 principles for deploying your API from a CI/CD pipeline" |
||||
|
date: 2019-07-26T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
At Red Hat, we strongly believe an API is not “just another piece of software.” Instead, we think an API is a software component in conjunction with: |
||||
|
|
||||
|
An interface to communicate with it. |
||||
|
An ecosystem of consumers that communicate with this software. |
||||
|
A relationship with developers consuming this API. |
||||
|
An API is built, deployed, and managed not just with the usual methods; as a result, deploying your API from a CI/CD pipeline requires additional processes, tools, and skills. |
||||
|
|
||||
|
In this article, we will focus on the overarching principles and key steps to deploy your API from a CI/CD pipeline. |
||||
|
|
||||
|
[Continue reading](https://developers.redhat.com/blog/2019/07/26/5-principles-for-deploying-your-api-from-a-ci-cd-pipeline/) |
||||
@ -0,0 +1,7 @@ |
|||||
|
--- |
||||
|
title: "Writing" |
||||
|
date: 2019-11-07T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
Here is a list of my recent articles. |
||||
@ -0,0 +1,9 @@ |
|||||
|
--- |
||||
|
title: "Deploy your API from a Jenkins Pipeline" |
||||
|
date: 2019-07-30T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
In a previous article, 5 principles for deploying your API from a CI/CD pipeline, we discovered the main steps required to deploy your API from a CI/CD pipeline and this can prove to be a tremendous amount of work. Hopefully, the latest release of Red Hat Integration greatly improved this situation by adding new capabilities to the 3scale CLI. In 3scale toolbox: Deploy an API from the CLI, we discovered how the 3scale toolbox strives to automate the delivery of APIs. In this article, we will discuss how the 3scale toolbox can help you deploy your API from a Jenkins pipeline on Red Hat OpenShift/Kubernetes. |
||||
|
|
||||
|
[Continue reading](https://developers.redhat.com/blog/2019/07/30/deploy-your-api-from-a-jenkins-pipeline/) |
||||
@ -0,0 +1,11 @@ |
|||||
|
--- |
||||
|
title: "Full API lifecycle management: A primer" |
||||
|
date: 2019-02-25T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
APIs are the cornerstone of so many recent breakthroughs: from mobile applications, to the Internet of Things, to cloud computing. All those technologies expose, consume, and are built on APIs. And those APIs are a key driver for generating new revenue. Salesforce generates 50% of its revenue through APIs, Expedia generates 90% of its, and eBay generates 60% of its. With APIs becoming so central, it becomes essential to deal with full API lifecycle management. The success of your digital transformation project depends on it! |
||||
|
|
||||
|
This article describes a set of full API lifecycle management activities that can guide you from an idea to the realization, from the inception of an API program up to management at scale throughout your whole company. |
||||
|
|
||||
|
[Continue reading](https://developers.redhat.com/blog/2019/02/25/full-api-lifecycle-management-a-primer/) |
||||
@ -0,0 +1,16 @@ |
|||||
|
--- |
||||
|
title: "Manage your APIs deployed with Istio service mesh" |
||||
|
date: 2019-04-30T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
With the rise of microservices architectures, companies are looking for a way to connect, secure, control, and observe their microservices. Currently, a service mesh such as Istio is the best option to reach this goal. |
||||
|
|
||||
|
- **Connect**: Istio can intelligently control the flow of traffic between services, conduct a range of tests and upgrade gradually with blue/green deployments. |
||||
|
- **Secure**: Automatically secure your services through managed authentication, authorization, and encryption of communication between services. |
||||
|
- **Control**: Apply policies and ensure that they are enforced and that resources are fairly distributed among consumers. |
||||
|
- **Observe**: See what’s happening with rich automatic tracing, monitoring, logging of all your services. |
||||
|
|
||||
|
And, as explained in “Distributed microservices architecture: Istio, managed API gateways and, enterprise integration”, a service mesh does not relieve the need for an API management solution. A service mesh manages services and the connections between them, whereas an API management solution manages APIs and their consumers. In this article, I’ll describe how to manage APIs using the Red Hat Integration adapter for Istio. |
||||
|
|
||||
|
[Continue reading](https://developers.redhat.com/blog/2019/04/30/manage-your-apis-deployed-with-istio-service-mesh/) |
||||
@ -0,0 +1,13 @@ |
|||||
|
--- |
||||
|
title: "Red Hat Single Sign-On: Give it a try for no cost!" |
||||
|
date: 2019-02-07T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
In a software world where each day is more hostile than the previous one, security matters and developers are coping with more and more non-functional requirements about security. The most common ones are the “OWASP Top 10”: the ten security risks that every developer should know. There are many more security risks you should care about, but those ten risks are the ones having the most impact on the security of your software. Among them are authentication and access control. |
||||
|
|
||||
|
The good news is that authentication and access control are now commodities in the open source world, thanks to Red Hat Single Sign-On Red Hat Single Sign-On is an access management tool that takes care of the details of most authentication protocols such as SAML, OAuth, and OpenID Connect; user consent with UMA; and even access control. It is easy to use, is very well-documented, and has a very active community: Keycloak. |
||||
|
|
||||
|
This article describes how to download and install Red Hat Single Sign-On for no cost. |
||||
|
|
||||
|
[Continue reading](https://developers.redhat.com/blog/2019/02/07/red-hat-single-sign-on-give-it-a-try-for-no-cost/) |
||||
@ -0,0 +1,13 @@ |
|||||
|
--- |
||||
|
title: "Using a public certificate with Red Hat Single Sign-On/Keycloak" |
||||
|
date: 2019-02-06T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
When deploying Red Hat Single Sign-On/Keycloak for a test or a proof of concept, most users will choose to use a self-signed certificate as explained in the official documentation. |
||||
|
|
||||
|
The setup instructions are straightforward, but this self-signed certificate will trigger certificate error messages in your web browser and can also prevent some clients such as Postman from working properly. |
||||
|
|
||||
|
This article explains how to use a public certificate from Let’s Encrypt with Red Hat Single Sign-On. |
||||
|
|
||||
|
[Continue reading](https://developers.redhat.com/blog/2019/02/06/using-a-public-certificate-with-red-hat-single-sign-on-keycloak/) |
||||
@ -0,0 +1,9 @@ |
|||||
|
--- |
||||
|
title: "Using the 3scale toolbox Jenkins Shared Library" |
||||
|
date: 2019-07-31T00:00:00+02:00 |
||||
|
draft: false |
||||
|
--- |
||||
|
|
||||
|
In the previous article of this series, Deploy your API from a Jenkins Pipeline, we discovered how the 3scale toolbox can help you deploy your API from a Jenkins Pipeline on Red Hat OpenShift/Kubernetes. In this article, we will improve the pipeline from the previous article to make it more robust, less verbose, and also offer more features by using the 3scale toolbox Jenkins Shared Library. |
||||
|
|
||||
|
[Continue reading](https://developers.redhat.com/blog/2019/07/31/using-the-3scale-toolbox-jenkins-shared-library/) |
||||
|
After Width: | Height: | Size: 43 KiB |
Loading…
Reference in new issue