Christina Lin is the Technical Marketing Manager for Red Hat Middleware Integration Products. She helps to grow market awareness and establish thought leadership for Fuse, AMQ and 3scale. By creating online videos, getting started blogs and also spoke at many conference around the globe. She has worked in software integration for the finance, telecom, and manufacturing industries, mostly architectural design and implementation. These real life system experiences helps her to be practical and combining open source technology, she hopes to bring more innovative ideas for the future system development.
Microservices is probably one of the most popular buzz words among my fellow developer friends, and I do like the concept of being flexible, agile and having simply having more choices. But as a person that worked in the software integration space for years, I started to see some resemblance of the old ESB days. Looking at the problem from ten thousand feet up. A decade ago, we had to come up with a better way of organizing the spaghetti...
Integration is still around but in a different form. So, what does modern integration look like? Looking at how agile scrum has taken over traditional waterfall development framework, by enabling shorter delivery cycles, faster feedback, and having the flexibility to rapidly adapt to changes. I believe it’s time for traditional integration to be agile again. By breaking up traditional ESB into distributed microservices. A little recap of what should be in Agile integration: Distributed Integration Lightweight, support distributed deployment Pattern...
I wanted to blog about this for a very long time, but because of work and being too lazy to turn on my laptop on the weekends, I now finally have a couple of hours to sit down and start blogging. "Integration is DEAD." "No, no, let's talk about microservice!" "What is that again? Integration, you mean SOA? It's lame...". During my recent conversations with many people about Integration, these comments came up a lot. In fact, if you happen...
Today, I am very pleased to announce the GA of Fuse Integration Service 2.0. This release will make integration applications more portable, flexible and allow agile developers to react faster to business needs by supporting microservice architectures. Developers will now be able to realize the benefits of microservices within integration projects and be able to leverage integration patterns while breaking up monolithic applications and reducing the size of services pushed onto older ESB technology. With FIS 2.0, developers can now...
A-MQ 7 Beta provides fast, lightweight, and secure messaging for Internet-scale applications. It sets a strong foundation for building modern distributed reactive architecture. A-MQ offers the rich feature set and reliability that enterprise customers depend on. A-MQ gives you the strong foundation you need to build modern distributed applications. Messaging for enterprise applications - A-MQ Broker is a pure-Java multiprotocol message broker, with fast message persistence and advanced high availability modes. It is very highly optimized for general message use-cases...
API plays a huge part in modern integration architecture design, a good design will allow your application to thrive, a bad design will end up on the cold stone bench and eventually vanishes. :( Well, to avoid this tragedy from happening to our APIs, there are certain guidelines that we might want to consider to follow. I know there are many debates out there on the best practice of API design, and I don't think it will ever end. It...
To get started with FIS 2.0, for people who are just getting to know the technology, here is how I interpret it. Basically, it's divided into two aspects. 1. Integration development: FIS uses Apache Camel as the core technology that creates, orchestrates, and composes microservices into a super lightweight thin integration layer, and becomes the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or...
Red Hat Fuse Integration Service 2.0 tech preview was released a few weeks ago and as it's based on Red Hat OpenShift 3.3, which has pipeline capability on top of it (tech preview on OpenShift as well), you are able to get one step closer to a more automated and agile continuous integration. As well as, a deployment one-stop platform for us, the integration developer. For the pipeline to work on OpenShift, you need Jenkins installed and running. OpenShift uses...
Article
