In a previous blog post, we explained how to deploy an existing JBoss BRMS/Drools rules project onto an OpenShift DecisionServer. We created a decision/business-rules microservice on OpenShift Container Platform that was implemented by a BRMS application. The polyglot nature of a microservice architecture allowed us to use the best implementation (a rules engine) for this given functionality (business rules execution) in our architecture.
The project we used was an existing rules project that was available on GitHub. We did however not explain how one can create a project from scratch in the JBoss BRMS Business Central environment and deploy it on OpenShift Container Platform. That is what we will explore in this article.
Continue reading “Your first Business Rules application on OpenShift: from Zero to Hero in 30 minutes”
Unless you’ve been on a complete media blackout for the last year or so (entirely understandable) you’ve likely heard a lot about Serverless (or FaaS – Function as a Service). Serverless is a major shift in the way developers build and deliver software systems – it greatly simplifies development by insulating the developer from infrastructure concerns and pushes the envelope on cost and efficiency of execution.
Continue reading “Red Hat and Apache OpenWhisk”
At the Red Hat Summit in Boston earlier this month, one IoT event stood out from the rest – a CodeStarter hackathon that brought together 80+ IoT enthusiasts to learn, tinker, and build an end-to-end IoT solution. The result was a complete IoT application that seamlessly integrates across IT and OT (Operations Technologies).
Continue reading IoT Hackathon – CodeStarter @ Red Hat Summit
Building a docker formatted container image for a Node.js application
There are 2 main strategies for building an image for a Node.js Application. The most common strategy is simply using a
Dockerfile with a base image of something like
FROM node:4-onbuild. Then do a
docker build. This will produce an image with your application in it, ready to be run. This strategy is known as the
Docker strategy in an OpenShift BuildConfig.
Another strategy is using the
s2i tool for taking the application source from a repository and producing the image. A typical command would be.
s2i build firstname.lastname@example.org/me/myrepo.git bucharestgold/centos7-s2i-nodejs:latest myapp. With this strategy, there is no explicit
Dockerfile. It is known as the
Source strategy in an OpenShift BuildConfig.
Continue reading “Installing Node.js dependencies with Yarn via s2i builds and OpenShift”
As I mentioned prior to Red Hat Summit, there was a whole lot of activity around the complementary aspects of microservices, containers, open source, and cloud, so I’ve assembled this recorded set of sessions on the topic Cloud Native Development. Enjoy!
Continue reading “18 Recorded Sessions on Cloud Native Development – from Red Hat Summit”
The content of the previous post discussed creating the open-vm-tools container’s Dockerfile and automating its started up via systemd with a unit file.
Continue reading “Containerizing open-vm-tools – Part 2: Atomic CLI and Converting to a Systems Container”
JBoss Tools 4.4.4 and Red Hat JBoss Developer Studio 10.4 for Eclipse Neon.3 are here waiting for you. Check it out!
Continue reading “JBoss Tools and Red Hat Developer Studio Maintenance Release for Eclipse Neon.3”