Let JBoss partners do the talking

Let our partners do the talking

As a continuation of my last blog (“Thank you JBoss partners”) I’d like to summarize some  contributions that some of our partners have done to the 10th anniversary of JBoss in the Red Hat family, as well as to the launch activities of JBoss EAP 7. You can see additional information and partner quotes in the EAP7 partner ecosystem press release.

Digital Competitive Advantage and a Higher Level of Customer Engagement with EDB Postgres and Red Hat JBoss

An example of how ISVs trust JBoss EAP in the new world of digital transformation is EnterpriseDB. Pierre Fricke, Vice President of Product Marketing and long-time JBoss veteran, explains in his guest blog how “EDB Postgres and Red Hat JBoss Enterprise Application Platform together provide deployment flexibility to deliver a total application and data platform that transforms IT and drives digital business.”

Continuous Delivery to JBoss EAP and OpenShift with the CloudBees Jenkins Platform

The CloudBees Jenkins Platform now supports integrations with both Red Hat JBoss Enterprise Application Platform (EAP) and Red Hat OpenShift across the software delivery pipeline. In this guest blog Cloudbees shares examples of how these enable developers to build, test and deploy applications, with Jenkins-based continuous delivery pipelines in JBoss via JBoss EAP 7 or JBoss EAP 7 on OpenShift.

JBoss EAP 7: The 7 New Features You Need to Know About!

Farhan Hussain from OpenSource Architect describes in this guest blog some of the key contributions of EAP7. Implementation of the Java EE 7 specifications that provide stability and standardization. Enhanced Management and Security. A Consistent and Easy to Manage Load Balancer. Rolling Upgrades To Minimize Downtime. An Offline CLI for Security and Initial Setup. Enhanced Modularity. You name it!

How akquinet approaches IoT with JBoss EAP7 and ActiveMQ Artemis

The new EAP7  messaging subsystem is based on the unified messaging technology for Red Hat products, Apache ActiveMQ Artemis. Heinz Wilming from akquinet presents in this blog an example of an architecture and technology stack where JBoss EAP7 and ActiveMQ Artemis are combined to face some of the challenges of IoT solutions.

JBoss EAP 7 and NoSQL using Java EE and Docker

For those that zero in on NoSQL and from a more technical perspective, Arun Gupta from Couchbase shares a guide to get started with NoSQL with JBoss EAP 7.

JBoss EAP 7: An Enterprise-Grade Microservice Platform

Derrick Sutherland from Shadow-Soft shares in this guest blog how JBoss has come a long way in terms of improving performance as well as truly innovating in regards to the way applications run and are managed. Among other, an extremely low-memory footprint for high density deployments, reduced start-up time or optimized networking port utilization, ideal for running within linux containers.

In addition some others sent us their thoughts!

Jun Tanaka, director and CTO, WingArc1st, Inc.

WingArc1st SVF is installed in more than 18,000 companies as an enterprise printing platform, which supports mission critical operations in financial, public, manufacturing, retail, logistic and services industry. An enterprise printing platform needs to be highly reliable, stable and provide high performance for seamless operations. WingArc1st believes that Red Hat Enterprise Linux and JBoss EAP7 are the important platforms for SVF.

Hiroyuki Yamamoto, director, monoplus, Inc.

With the rise in data and services, the performance and quality of ICT infrastructure is becoming more and more critical. As business environments continue to evolve, we believe that Red Hat JBoss Middleware can seamlessly contribute and support in the integration, co-operation and collaboration within businesses. With this strong support, monoplus hopes to provide a solution that connects customers’ mission critical systems and ICT infrastructure using JBoss EAP 7 and JBoss Fuse.

Hisanao Takei, senior executive officer and general manager, ProActive Business Solutions Div.

SCSK welcomes the JBoss EAP 7 release. ProActive E2 is an ERP package solution that has been installed in more than 5,500 companies in Japan. ProActive E2 supports companies with quick decision-making based on consolidated business process and centralized managed data. SCSK chose JBoss EAP 7 as their platform to meet their needs of open source software. SCSK thinks JBoss EAP 7 is the best choice that customers want for building open and standard infrastructure and especially expects system TCO reduction for virtual and cloud environment.

Regis Kuzel Sr. VP of Business Development Sales, LCN Services

LCN is a trusted advisor to our customers. They appreciate our knowledge, expertise and especially how unbiased we are when it comes to recommending the right technology to meet their requirements. When it comes to making a decision on which Application Platform to run your mission critical and customer-facing applications, it’s more important than ever. IT requirements are changing. The need to be well informed and seek expert advice is critical in order to make the right decisions for your organization. For LCN, the bottom line is you can’t do better than Red Hat’s EAP7. It’s a well thought out platform. And it’s gaining market share because it works! Red Hat EAP7 is the best technology available at its core!

Ivan Cardona, owner, Opticca

We’ve been been deploying middleware, SOA, and BPM platforms from the major providers for the past eight years. We’ve recently made a large investment In Red Hat’s JBoss solutions because our customers’ feedback led us to conclude open source is now a real option. Our customers experienced tremendous success deploying services and business processes leveraging these platforms. The challenge they face is the solutions are too expensive to scale further and/or many find the platform overhead is too heavy. Red Hat’s Jboss solutions directly address those two concerns. For this reason we are very bullish on Red Hat’s ability to gain a substantial portion of the middleware, BPM, container, and micro services market.

Matt Pavlovich, Co-Founder and Technical Practice Lead, Media Driver

The release of EAP7 brings an exciting array of new features and capabilities to Enterprise Developers. EAP7 is the defacto standard for the Java EE 7 specification running on the Java 8 JDK and Media Driver is excited about the latest features available to developers. Having all the key Java specifications certified to work together allows developers to be more efficient by focusing their time on delivering business value versus fiddling with tech stacks. Whether it is deployed on-premise, in the cloud or via containers, EAP7’s deployment flexibility ensures DevOps teams will not have to navigate tricky hurdles to get their environments up and running quickly. Enterprise grade features with flexible support options make JBoss EAP7 an easy decision.

Farhan Hussain, Founder and CEO, Open Source Architect

As a leading Red Hat partner with hundreds of successful JBoss implementations in the books, JBoss EAP 7 is going to be a very important release for our comprehensive portfolio of Red Hat solutions and services. Consistent customer success is the force that drives us to say with confidence that Red Hat’s JBoss Enterprise Application Platform (EAP) is the *only* choice for organizations seeking an open source, market-leading Java EE application platform. This new platform will help us provide reliable, cost-efficient and high-performing container-based solutions for on-site and cloud deployments, while enabling our joint customers to innovate and meet strict compliance, security, and regulatory requirements simultaneously!

Bob and Kathy Cartwright, owners, Dimension Systems

JBoss EAP7 support of Java EE7 allows customers the flexibility to meet their requirements without restrictions. Dimension Systems sees the value in Red Hat being a leader in this front. EAP 7 is bringing an updated manage console which will improve the user interface experience. Ease of navigation and support for large scale domain configurations is a big customer win.

Again, thank you Red Hat partners. You made our decade.

And for those that are still not in the ecosystem, please join us. We’re here to help you grow.

Thank you JBoss partners

Thank you JBoss partners. You made our decade.

In the open source world (and I would say increasingly in the software world in general), the success of a new technology begins with active and vibrant communities that crank out compelling and useful technologies.

When the technology gets out and increases in popularity, early customers begin to trust it and it faces the challenge of being adopted by the mainstream market, which is composed predominantly by customers who are pragmatists in nature and that find it difficult to use a new product unless it has support in the market (other customers) and it has an ecosystem of partnerships and alliances with other vendors that serve their industry.

That’s why partners are key to technology products. The larger the partner ecosystem, the more trust customers can have and the better the chances of widespread adoption.

JBoss had started to create that partner ecosystem before it became part of the Red Hat family back in 2006. Many things have happened since those early years, and we’ve probably done a few right things along the way, as Red Hat has become the first open source company to surpass the two-billion-dollar revenue mark, and for the fourth consecutive year we have been awarded a 5-Star rating in the CRN 2016 Partner Program Guide – where vendor applications are assessed based on investments in program offerings, partner profitability, partner training, education and support, marketing programs and resources, sales support, and communication.

However, at the end of the day, it is really the partners who decide which technology partners they choose to pursue success in the marketplace.

In anticipation of the launch of Red Hat JBoss Enterprise Application Platform 7 (JBoss EAP), and of the 10th anniversary of JBoss becoming part of the Red Hat family, we offered our partners the opportunity to tell the world about out our collaboration.

So don’t take our word for it. Let our partners do the talking.

We are fortunate to have partners that have worked with JBoss for a long, long time. Some of them, such as Vizuri, were a JBoss partner before it became part of the Red Hat product family. Joe Dickman, senior vice president, explains that the widespread adoption of JBoss in the marketplace, especially among Fortune 500 companies, is “a testament to the ‘power of community collaboration and innovation’ that Red Hat embodies, which has forever changed the way that software is developed and businesses operate.”

Another JBoss veteran is Viada in Germany. In words of Daniel Braunsdorf, CEO of Viada in Germany, “Ten years ago JBoss was the first open source application server being really ‘enterprise-ready’”, and today “we are talking about a full stack of middleware suite products serving our customers needs by giving them more flexibility, agility, and speed to deliver innovative applications.”

James Chinn, CEO of Shadow-Soft, sums it up well: “Over the last decade, JBoss has come a long way in terms of improving performance as well as truly innovating in regards to the way applications run and are managed. With the release of JBoss EAP 7 comes a host of new features including full support of Java EE 7 and Java SE 8 (…) Furthermore, JBoss EAP 7 has also been upgraded to reduce start-up time and optimize networking port utilization making it truly ideal for running within Linux containers.”

SCSK from Japan trust the power of JBoss EAP 7 to drive open standardization and TCO reduction. In the words of Hisanao Takei, Senior Executive Officer, “SCSK thinks JBoss EAP 7 is the best choice that customers want for building open and standard infrastructure and especially expects system TCO reduction for virtual and cloud environment.”

Red Hat JBoss Middleware is at the core of many mission critical systems. And being intimately related with the other Red Hat middleware products, such as JBoss Fuse, enables our partners to support many different types of business customer needs. Hiroyuki Yamamoto, director at monoplus, Inc. in Japan, makes the point that “As business environments continue to evolve, we believe that JBoss Middleware will seamlessly contribute and support in the integration, co-operation and collaboration within businesses”.

Driven by the dynamism of information based sectors, it may be easy to forget that traditional businesses also need advanced enterprise systems to be successful. In such a traditional business as printing, our Japanese partner WingArc1st makes the point that “An enterprise printing platform needs to be highly reliable, stable and provide high performance for seamless operations,” and believe that “Red Hat Enterprise Linux and JBoss EAP 7 are important platforms” for the company’s SVF offering.

Matt Pavlovich, co-founder of Media Driver, abounds on how JBoss EAP 7 helps developers “to be more efficient by focusing their time on delivering business value versus fiddling with tech stacks.” No small feat, as he continues, “Whether it is deployed on-premise, in the cloud or via containers, JBoss EAP 7 provides deployment flexibility that can help DevOps teams avoid having to navigate tricky hurdles to get their environments up and running quickly.”

Regis Kuzel, senior vice president at LCN Services, takes pride at being an unbiased trusted advisor to their customers. “For LCN, the bottom line is you can’t do better than Red Hat JBoss EAP 7. It’s a well-thought-out platform. And it’s gaining market share because it works! We believe Red Hat JBoss EAP 7 is the best technology available at its core!”

In terms of innovation, Farhan Hussain, Founder and CEO, Open Source Architect has a clear view of the contribution of the new EAP7. “This new platform will help us provide reliable, cost-efficient and high-performing container-based solutions for on-site and cloud deployments, while enabling our joint customers to innovate and meet strict compliance, security, and regulatory requirements simultaneously!” says Farhan.

Heinz Wilming, Director, Red Hat JBoss Competence Center for our German partner akquinet, makes a point about the value that long term support provides to our common customers. As you are possibly aware, Red Hat JBoss Middleware product life cycles are generally three, five, or seven years in length, and for certain products can be extended by three (3) additional years (up to ten!), something not many vendors actually provide. In his words, “Long-lasting support, regular updates and interoperability ensure protection of investment and guaranteed future for both our customers and akquinet.”

Some of our partners have been supporting JBoss for a long time, and others have made investments more recently. This is the case of Opticca in Canada. Owner Ivan Cardona shares that “We’ve been deploying Middleware, SOA, and BPM platforms from the major providers for the past eight years. We’ve recently made a large investment In Red Hat’s JBoss solutions because our customers’ feedback led us to conclude open source is now a real option.”

A last word…

We are really happy we are getting this support from our partners. Many others share us in the 10th anniversary and you can learn more from our strategic alliances here. And find more in the JBoss partner ecosystem press release, here.

And for those that are still not in the ecosystem, please join us. We’re here to help you grow.

So let me conclude as I began.

Thank you, Red Hat partners. You made our decade. Ready for more?

PD: Keep reading here for blogs and additional quotes from partners worldwide about the new EAP7!

Building an API-Based Connected Healthcare Solution: Q&A Followup

Christina Lin (a technology evangelist for Red Hat) and Sameer Parulkar (middleware product marketing manager for Red Hat) conducted a webinar earlier this week about data integration challenges which specifically face healthcare providers. As promised, this is a brief roundup of the major questions that came out of the webinar and pointers to more detailed information about the demo. (If you would like more background on integration challenges in healthcare, we do have posts on integration architecture for healthcare and another on how to overcome integration challenges.)

A Quick Summary

The recording of the full webinar is available here, but I’ll summarize it briefly if you can’t watch it yet.

Continue reading “Building an API-Based Connected Healthcare Solution: Q&A Followup”

Intro to Scalability

Scalability is one of those words that can mean very different things to different people, even in the same context or the same project. It’s not so much nuanced as it is that the definition matters on perspective — scale can be different for different goals.

There will be upcoming posts on data virtualization, in-memory data grids, integration methods — all areas where an understanding of your current and future needs, resourcing, and loads are critical for planning. Going into those concepts, it helps to understand scale — not just “make it bigger,” but how you make it bigger and when and why.

Continue reading “Intro to Scalability”

If All Men Were Angels…

If all men were angels, no government would be necessary.

James Madison made the case that no system is perfect precisely because people aren’t perfect. That was, admittedly, a defense of a political revolutionary moment, but it holds true in software design as well.

Mark Little, vice president of engineering for middleware at Red Hat, has a blog post on this topic this week on jboss.org. The entire post is terrific (and readably brief), but there are a couple of points worth highlighting. His premise starts with the idea of what causes (or devolves) a system into a monolith, and he points to this:

Lack of architect (leadership); the original architect(s) leave the project and those who come in to replace them (if they are replaced) can’t control the developers or perhaps don’t understand the architecture enough to ensure it remains “pure”. Likewise, different developers coming into the project to either add to or replace those there already, can dilute the group knowledge and understanding of the architecture, leading to unforeseen and accidental divergence from the original plan.

What leads to an inflexible, centralized monolith application is, ironically, a lack of central vision. Mark sums it up with a really good point about the risks in microservice architectures:

I believe in and understand the need for distributed systems composed of (micro) services. However, what worries me about some of the current emphasis around microservices is that somehow they will naturally result in a better architecture. That’s simply not the case. If you don’t put in to place the right processes, design reviews, architecture reviews, architects etc. to prevent or forestall a local monolith then you’ve no hope of achieving a good microservices architecture. [emphasis added]

This is such an amazing point, it bears repeating. There is frequently this unspoken, sometimes unrecognized, belief that The Next Good Thing will some how solve all of the issues of the Last Good Thing without requiring special effort. But there are no perfect systems — clear planning, good communication, good team processes are required no matter what architectural pattern you’re using to develop your applications.

 

“Tech Preview”: A Look at Wildfly Swarm

The story of Wildfly Swarm, from a business perspective, is kind of a story of microservices. Microservices are small, isolated, and focused service applications; as an architecture, microservices is an approach that decomposes larger systems into those smaller, focused, isolated services. These services talk to each other through a shared, common API, but are otherwise independent in design and deployment. Microservices, then, are frequently aligned with DevOps – which uses small, agile teams to quickly develop and push software for continuous integration (of systems) and continuous delivery (of software).

But what is Wildfly Swarm, in that context.

Continue reading ““Tech Preview”: A Look at Wildfly Swarm”

Intro to Microservices

An increasingly common buzzword in cloud computing is microservices. Like a lot of things associated with cloud technologies, a precise definition is difficult to find — and it can mean a lot of things to a lot of different people, depending on the context. Since this is a blog devoted to middleware issues, I want to define microservices within the context of that middle layer in computing, for application development.

A Definition

Microservices is an architectural approach for a software system. Meaning, it defines how individual services fit together and how those services are constructed (like, general constraints or best practices). What sets microservices apart from other architectural approaches is that it treats each service as a discrete and independent part of the architecture. That means that services themselves (within that system) have very clear definitions:

Continue reading “Intro to Microservices”