Daniel Oh

Senior Principal Technical Marketing Manager, CNCF Ambassador, DevOps Institute Ambassador, Developer, Speaker, Writer, Opensource.com Correspondent, @quarkusio @redhat

Areas of Expertise

Cloud-Native App Dev

Recent Posts

Build even faster Quarkus applications with fast-jar

Build even faster Quarkus applications with fast-jar

Quarkus is already fast, but what if you could make inner loop development with the supersonic, subatomic Java framework even faster? Quarkus 1.5 introduced fast-jar, a new packaging format that supports faster startup times. Starting in Quarkus 1.12, this great feature became the default packaging format for Quarkus applications. This article introduces you to the fast-jar format and how it works.

Continue reading Build even faster Quarkus applications with fast-jar

Share
Enhancing the development loop with Quarkus remote development

Enhancing the development loop with Quarkus remote development

Kubernetes is an established foundation layer for cloud-native microservices and serverless architectures. By automating application deployment, scaling, and management, Kubernetes changes the developer’s daily workflow in terms of inner loop development (local coding, building, running, and testing the application) and outer loop development (integration testing, continuous deployment, and security). Developers using Kubernetes also must plan for containerization, debugging code inside pods, and automating test cases.

Continue reading Enhancing the development loop with Quarkus remote development

Share
Write a Quarkus function in two steps on Red Hat OpenShift Serverless

Write a Quarkus function in two steps on Red Hat OpenShift Serverless

Serverless functions are driving the fast adoption of DevApps development and deployment practices today. To successfully adopt serverless functions, developers must understand how serverless capabilities are specified using a combination of cloud computing, data infrastructure, and function-oriented programming. We also need to consider resource optimization (memory and CPU) and high-performance boot and first-response times in both development and production environments. What if we didn’t have to worry about all of that?

Continue reading Write a Quarkus function in two steps on Red Hat OpenShift Serverless

Share
Build embedded cache clusters with Quarkus and Red Hat Data Grid

Build embedded cache clusters with Quarkus and Red Hat Data Grid

There are many ways to configure the cache in a microservices system. As a rule of thumb, you should use caching only in one place; for example, you should not use the cache in both the HTTP and application layers. Distributed caching both increases cloud-native application performance and minimizes the overhead of creating new microservices.

Continue reading Build embedded cache clusters with Quarkus and Red Hat Data Grid

Share
Analyze monolithic Java applications in multiple workspaces with Red Hat’s migration toolkit for applications

Analyze monolithic Java applications in multiple workspaces with Red Hat’s migration toolkit for applications

Transforming monolithic Java applications into distributed, cloud-native microservices is never easy, but Red Hat’s migration toolkit for applications helps you understand and evaluate the migration path. As a developer, you can apply the following features to a broad range of transformation use cases:

Continue reading Analyze monolithic Java applications in multiple workspaces with Red Hat’s migration toolkit for applications

Share
Cloud-native modernization or death? A false dichotomy

Cloud-native modernization or death? A false dichotomy

DevNation Tech Talks are hosted by the Red Hat technologists who create our products. These sessions include real solutions plus code and sample projects to help you get started. In this talk, you’ll learn about cloud-native modernization from Daniel Oh and Burr Sutter.

Are you familiar with the tight coupling of applications with their underlying platform that makes change hard? Or, coupling that creates a lack of scalability, performance, and flexibility for existing applications built with legacy technology? How about the fact that re-architecting applications cannot be done overnight?

Continue reading “Cloud-native modernization or death? A false dichotomy”

Share