12 Simple Tips for Your Next Highly Available Cloud Buildout

Situation: You’re a great software developer and a fearless leader. Your CEO bursts into your cubicle and he is giving you vast amounts of investment capital, no data center, and limited staff. Your task: build a multi-region, highly available presence in AWS (or your favorite cloud provider) that can be maintained by minimal man-power. Your multi-tier Java EE app is almost ready. You are going to be required to create, maintain, and monitor a large amount of servers, RDS instances, S3 buckets, queues, public DNS entries, private DNS entries, etc. This series of articles aims to provide some ideas that help you go to market without a snag.

You heard multiple servers and you started to build your Ansible tower, puppet master, chef recipes, glue scripts. STOP!

Before you get yourself into a situation where your company is paying your favorite coffee shop’s franchise fee in cloud services and is getting the functionality of a french press, let’s think this through. There are a few things you need to consider. Are you creating EC2 instances manually? What is your staging environment like? Do you have one? Where should it live? Let’s take a few moments and discover the steps we need to take using the flowchart in Figure 1.

Figure 1: HA Cloud build out demands the use of an IAC tool set.

Note: The toolset we chose is Hashicorp Terraform [] as our Infrastructure as Code (IAC) tool, and puppet community [] for configuration management. If you choose a different set of tools, the principles in this series will still apply. As an obvious caveat, some scripts may not work, and please substitute your tools’ names in your head while following along.

Continue reading “12 Simple Tips for Your Next Highly Available Cloud Buildout”


Red Hat Keynote Mobile App

This year’s middleware keynote address at Red Hat Summit talked about microservices, the power of the pipeline, and how developers and devops can work together to release code to production at a much higher rate.

The keynote also demonstrated how releases can be shipped so you can switch from the existing deployment to a new deployment (blue/green deployments), and demonstrated how to roll out a canary deployment to a subset of users to test out new features. (If the canary “dies”, roll the deployment back. If it lives, gradually ramp up the release of the deployment until all users receive the new code. )

To show all of this off, we needed to create something visual, where users could see the deployments change right in front of their eyes. That’s where the Red Hat Keynote Mobile Application came in.

Continue reading “Red Hat Keynote Mobile App”


Considerations for Implementing JBoss Fuse in your Enterprise

In today’s modern world, the need for enterprise integration has never been greater. Companies are looking for ways to reduce the costs of their application infrastructure and one of the ways they are doing that is by extending the lifespan of older legacy platforms. This introduces a number of problems when there is also a need for the implementation of new modern systems as well. Often times it is difficult if not impossible to make these new and legacy systems communicate directly. To resolve this problem, many companies are considering adopting Red Hat JBoss Fuse to integrate these systems together.

If you are considering implementing JBoss Fuse in your company’s enterprise there are several key pieces of information you need in order to make an informed decision. This starts with what JBoss Fuse really is, and what are the options for deploying it?

Continue reading “Considerations for Implementing JBoss Fuse in your Enterprise”


Account Management with JBoss BPM Suite

Red Hat’s IT department recently deployed JBoss BPM Suite to handle automated process workflow. JBoss BPM Suite is officially defined as:

An open source business process management suite that combines Business Process Management and Business Rules Management and enables business and IT users to create, manage, validate, and deploy Business Processes and Rules.

IT’s immediate use case is to replace our aging account management system, which is essentially a collection of perl and python scripts.  Some of these date back to the turn of the millennium. These scripts had the responsibility of handling all aspects of user life cycle management, including:

  • Pulling user data from the HRMS
  • Creating the user LDAP object
  • Creating the user group LDAP object
  • Creating application accounts (home directories, mailboxes, etc)
  • Updating LDAP objects with HRMS changes
  • Closing user accounts and removing LDAP objects upon termination
  • Syncing account information with third party systems (SaaS vendors, etc)

These legacy scripts would perform SQL queries directly against multiple data sources and call LDAP operations, application command line tools and make API calls. While this system worked well for many years, maintenance became an incredible burden. In essence, only one person knew the account automation system. New application integration requests would have to wait months for resources to free up. For applications allowing direct API integration, that meant some pour soul (me) would have to spend a fair amount of time just figuring out how this new application worked and what API calls were necessary. Moreover, when a vendor would suddenly change their API, that meant something was broken until there was time to fix it. The result was Service Desk team having to perform hundreds of manual operations in the mean time. Essentially, the maintainer could not scale with demand, let alone have the time to become an expert in every new application.

Continue reading “Account Management with JBoss BPM Suite”


API Management with JBoss Fuse on Openshift and 3scale on Amazon Web Services – Part 1


A way organizations deal with the progression towards a more connected and API driven world, is by implementing a lightweight SOA/REST API architecture for application services to simplify the delivery of modern apps and services.

In the following blog series, we’re going to show how solutions based on 3scale and Red Hat JBoss Fuse enable organizations to create right interfaces to their internal systems thus enabling them to thrive in the networked, integrated economy.

Among the API Management scenarios that can be addresses by 3cale and Red Hat with JBoss Fuse on OpenShift, we have selected to showcase the following:

  1. Scenario 1 — A Fuse on Openshift application containing the API. The API is managed by 3scale with the API gateway hosted on Amazon Web Services (AWS) via the 3scale AMI.
  2. Scenario 2 — A Fuse on Openshift application containing the API. The API is managed by 3scale with the API gateway hosted via APIcast (3scale’s cloud hosted API gateway)
  3. Scenario 3 — A Fuse on Openshift application containing the API. The API is managed by 3scale with the API gateway hosted on Openshift

Continue reading “API Management with JBoss Fuse on Openshift and 3scale on Amazon Web Services – Part 1”


Using JBoss Fuse and 3scale for API Management

Since Red Hat and 3scale announced our partnership a year ago, we’ve seen great interest by companies and developers to use JBoss Middleware with 3scale API management technology (check out the solution brief here: Enabling success in the API economy).

In this webinar recording, we introduced you to how you can manage and control APIs (including a practical demo) using Red Hat® JBoss® Fuse, OpenShift by Red Hat, and 3scale.

Continue reading “Using JBoss Fuse and 3scale for API Management”