Product Manager
Bilgin Ibryam
Bilgin Ibryam is a former product manager and architect at Red Hat. He is a regular blogger, open source evangelist, speaker, and the author of Camel Design Patterns and co-author of Kubernetes Patterns books. He has over a decade of experience in designing and building scalable and resilient distributed systems. In his day-to-day job, Bilgin works with customers from all sizes and locations, helping them to be successful with adoption of emerging technologies through proven and repeatable patterns and practises. His current interests include event-driven systems, blockchains, cloud-native and serverless. Follow him @bibryam for regular updates on these topics.
Bilgin Ibryam's contributions
Top 10 must-know Kubernetes design patterns
Bilgin Ibryam
Discover 10 design patterns from the Kubernetes Patterns book that will help you follow basic Kubernetes concepts and design Kubernetes-based applications.
First steps with the data virtualization Operator for Red Hat OpenShift
Bilgin Ibryam
We provide a step-by-step visual tutorial describing how to create a simple virtual database using Red Hat Integration's data virtualization Operator.
Architectural messaging solutions with Apache ActiveMQ Artemis
Bilgin Ibryam
Learn how to make the AMQ Broker architecting process, the resulting deployment topologies, and the expected effort more predictable for common use cases.
Subsecond deployment and startup of Apache Camel applications
Bilgin Ibryam
This article provides some history of Apache Camel and describes two new changes coming to Camel and why they are important for developers.
The rise of non-microservices architectures
Bilgin Ibryam
There are pros and cons using to a microservices architecture. Some teams decide not to strictly follow all the principles of the "pure" microservices architecture. This post explores some valid reasons for using or not using microservices, and it discusses alternatives.
Which Camel DSL to choose and why?
Bilgin Ibryam
Apache Camel is a powerful integration library
Hexagonal Architecture as a Natural fit for Apache Camel
Bilgin Ibryam
There are architectures and patterns that look cool on paper, and there are ones that are good in practice. Implementing the hexagonal architecture with Camel is both: cool to talk about, and a natural implementation outcome. I love going hexagonal with Camel because it is one of these combinations where the architecture and the tool come together naturally, and many end up doing it without realizing it. Let’s see why that is the case. Why go Hexagonal? Hexagonal architecture is...
Short Retry vs Long Retry in Apache Camel
Bilgin Ibryam
My Camel Design Patterns book describes 20 patterns and numerous tips and best practices for designing Apache Camel based integration solutions. Each pattern is based on a real world use case and provides Camel specific implementation details and best practices. To get a feel of the book below is an extract from the Retry Pattern section describing how to do Short and Long retires in Apache Camel. Context and Problem By their very nature, integration applications have to interact with...
Top 10 must-know Kubernetes design patterns
Discover 10 design patterns from the Kubernetes Patterns book that will help you follow basic Kubernetes concepts and design Kubernetes-based applications.
First steps with the data virtualization Operator for Red Hat OpenShift
We provide a step-by-step visual tutorial describing how to create a simple virtual database using Red Hat Integration's data virtualization Operator.
Architectural messaging solutions with Apache ActiveMQ Artemis
Learn how to make the AMQ Broker architecting process, the resulting deployment topologies, and the expected effort more predictable for common use cases.
Subsecond deployment and startup of Apache Camel applications
This article provides some history of Apache Camel and describes two new changes coming to Camel and why they are important for developers.
The rise of non-microservices architectures
There are pros and cons using to a microservices architecture. Some teams decide not to strictly follow all the principles of the "pure" microservices architecture. This post explores some valid reasons for using or not using microservices, and it discusses alternatives.
Which Camel DSL to choose and why?
Apache Camel is a powerful integration library
Hexagonal Architecture as a Natural fit for Apache Camel
Short Retry vs Long Retry in Apache Camel