Back in September last year I announced that we were working on xPaaS (enterprise services in the Cloud and specifically OpenShift). xPaaS is a long term effort that will evolve as our products evolve and we put them into the Cloud. However, it's with great pleasure that I can announce we've started the xPaaS releases with iPaaS (Integration-as-a-Service):

 

Screen Shot 2014-03-08 at 10.13.54.png

You can find out much more about iPaaS by checking out the home page and taking it for a test drive - give us feedback too! As Arun mentions separately, there will also be some relevant sessions at this year's DevNation. And we should be announcing further updates to the xPaaS effort in the coming months, so keep watching.

I've written a couple of blog entries on my personal blog which are related and which people may find interesting. The first is on some work I was doing over Christmas with CapeDwarf running on Raspberry Pis, with the aim to turn them into a private cloud. The second is about the adoption of hybrid cloud, but also repeats what I've been saying for several years that devices such as the Pi (or smaller) need to become part of the cloud. I'm hoping to say more about this at Summit later this year and maybe we'll have some demos to illustrate.

We've seen a couple of announcements already around DevNation and I just wanted to add my own take to this because I've been asked "Where's JUDCon or CamelOne?" The simple answer is that they haven't gone away, but at least as far as Summit is concerned they've been subsumed within DevNation. The reason for this is pretty simple too: when I kicked off JUDCon with the team back in 2010 it was the precursor event to JBossWorld/Summit and the only developer conference we held at that point. Over time we've added OpenShift and other developer conferences with non-JBoss focus and then of course last year we added CamelOne. Each of these conferences have their own identities but when gathered together at the same time and location it can cause confusion, not just in terms of questions like "If I register for JUDCon can I go to CamelOne?" but also in terms of presentations, which often span multiple developer communities and hence these individual conferences, resulting in questions like "Why was that presentation at JUDCon when it clearly should have been at CamelOne?"

 

Therefore, whilst the likes of JUDCon will continue to exist in isolation (you are going to JUDCon India, right?) and we've restarted the Fuse Days, when gathered together at Summit we'll have just DevNation. The content of this one event will be just as eclectic, the communities just as vibrant and the entertainment just as good, but now it should be a lot easier to understand just what you get for your registration and what you can expect. Of course I'm sure (I hope) there will still be issues with being able to see all of the sessions you want to see because some conflict, but I think that's the sign of a good conference/workshop.

 

Onward to DevNation!

Mark Little

Lyon JUG report

Posted by Mark Little Nov 29, 2013

I got the opportunity recently to go to Lyon (haven't been there in about 2 decades!) and present at INSA/CITI as well as give a session at the local JUG. Before I set off I was asked a few questions so that they could post an interview with me. If you're interested, then the interview is here.

 

I'm hoping that CITI and the Lyon JUG will eventually post the presentations I gave as they're a little bit too big to attach here. However, here's the first slide from my presentation at CITI:

 

Screen Shot 2013-11-29 at 13.25.51.png

And here's the equivalent from my JUG presentation:

 

Screen Shot 2013-11-29 at 13.28.01.png

Fortunately in this and age of social networking, I didn't have to worry about taking pictures of the event: others did that for me and I include them here along with my gratitude:

 

Screen Shot 2013-11-29 at 13.23.37.pngScreen Shot 2013-11-29 at 13.23.46.png

For those people who weren't there and want to see the last slide in more detail, here it is:

 

Screen Shot 2013-11-29 at 13.30.00.png

 

I want to thank everyone who attended both presentations and gave me some good questions to answer and things to think about on my journey home. I also want to thank Julien Ponge and Alexis Hassler for inviting me and arranging everything. I do want to do it again!

Mark Little

Sun-setting again

Posted by Mark Little Nov 6, 2013

Back in 2009 I wrote about how it was sad in some ways that Sun had been acquired by Oracle. 4 years later, we now hear that GlassFish is being relegated to the domain of the Reference Implementation. Once again I have mixed feelings about this event. Despite GlassFish being seen as a competitor to our own offerings, there was always a grudging respect for what that team had done, and several of them now work for Red Hat, often as a direct result of those efforts. So in that regard it is sad to see it go. However, what worries me the most about this turn of events isn't so much about the technology, but rather what signals this could send to their open source communities. I will leave that mainly as an exercise to the reader, but it doesn't really take a massive leap to be concerned if you are a member of those communities. Now I'm not going to suggest that Red Hat's projects such as WildFly, or any other open source vendor, are necessarily a better home for those community members who feel that it is time to move on, but I would hope that they would at least take a look and judge us on our track record.

I'm on holiday at the moment but some things are so important that they draw me back temporarily. Red Hat and JBoss before it, has been an active member of the JCP Executive Committee for many years. We've worked with Sun, Oracle, IBM, HP, JUGs and many others to try to ensure that Java the language and Java EE the platform, are open and fully participatory by those who really make our collective thriving ecosystem work. It hasn't always been easy but we're glad to be involved. Whether it's helping to open up the JCP processes, injecting more open source practices, leading JSRs or participating in them, we try to be involved in all aspects of the Java community and standards. This is why being on the JCP Executive Committee is important for Red Hat: we believe that the best way to influence things is from within and being on the Executive Committee gives us that ability.

 

But an even more important aspect of being on the JCP EC is that everyone gets voted on (or off). As with any election, this is a great way of getting feedback on how well people view you and your approaches. We've been elected on to the EC every time our seat has been up for election, but that does not mean that we take it for granted: far from it in fact! And this time is no different. The elections kicked off recently and myself and Scott Stark represented Red Hat. The results have just been reported and I'm really pleased and proud to report that we've been elected for another two years. As you can see from the results, we got a lot of votes and it pleases me that so many people believe we are doing a good job. I want to thank everyone who voted, whether or not they voted for us (voting is important!); we will ensure that your vote counts.

I wrote an article on InfoQ recently about IoT. This was based upon a presentation I saw whilst at the JCP EC meeting in September from ARM. I found it fascinating, especially given the work we've been doing on things like Raspberry Pis. It was also interesting to hear how important ARM and others see Java in this space. So if you haven't read the article then take a look.

Mark Little

xPaaS

Posted by Mark Little Sep 24, 2013

We've been talking about PaaS for several years now. Whether it's outlining our intentions around Enterprise PaaS and then delivering with the first EE6 Platform as a Service, discussing how EAP, EE6 and Java are critical for mobile and cloud, or many presentations and announcements at Red Hat Summits (exercise left to the reader to check these out), I think it's safe to say that we've been leading the push for Cloud, PaaS and relationships with Java. Last week we announced another key presentation update on our PaaS strategy that would happen at JavaOne and I'm pleased to say that's now happened and I can talk publicly about the work that our teams have been doing over the last few months.

 

We're terming this xPaaS because it is meant to encompass much more than what PaaS has typically come to be associated with (ePaaS, or Enterprise PaaS, is a component of xPaaS). In many ways we've been talking about xPaaS for a couple of years and particularly how technologies and methodologies such as SOA or integration must play within the Cloud and between users of the Cloud. But with the advent of mobile, obvious problems to come such as that indicated by Shannon's Limit, and other changes in the way our industry, xPaaS has come to encompass much more.

Screen Shot 2013-09-21 at 16.30.18.png

Some of our recent acquisitions, such as Fuse (Fabric, Camel), Polymita and efforts like AeroGear, WildFly, embedded device work (e.g., Raspberry Pi) etc. have all contributed to xPaaS in one way or another. We demo-ed some of this during this year's Summit JBoss keynote, and with iPaaS (Integration PaaS) James has been previewing it for many months. The xPaaS announcement brings all of this together and pretty soon developers will be able to use these technologies themselves and provide us with feedback as well as help to evolve it.

Screen Shot 2013-09-21 at 16.53.29.png

Some important highlights for the iPaaS component of xPaaS include: code-less UI - drag/drop/configure deploy - anywhere - public/private cloud, bare metal etc., cloud and SaaS connectors (via Apache Camel), auto-scaling to meet demand - all managed from a central platform, and of course it works on OpenShift.

 

As I mentioned already, mobile is an important part of Cloud today. So another part of xPaaS is our Push Server which runs on OpenShift and has AeroGear at its heart. But some important things to note about this release is that we have integration with iOS (APNS), Android (GCM), and FFOS/Web (Mozilla SimplePush), with associated client SDKs. There are also sender SDKs for Java, with Node.js, and PHP in development.

Screen Shot 2013-09-21 at 17.02.34.png

And of course just as outside of the Cloud, once you start to create your applications from components and services, BPM (in the form of jBPM, for instance) and related technologies such as BAM, become a necessity. So of course BPM-as-a-Service is an integral part of xPaaS.

 

Screen Shot 2013-09-21 at 17.07.15.png

Of course I can only give you a taster of what we've just announced. You'll hear more from us over the next weeks and months as we roll out these xPaaS components so you can try them out. Our end goal is supported products and we'll be making other announcements later. For now check out the xPaaS announcement and watch this space. This is when PaaS really enters the enterprise domain!

 

And a big congratulations to everyone in the teams within Red Hat who have been involved in this announcement and the technologies it showcases! It's a great effort!

Mark Little

CapeDwarf

Posted by Mark Little Aug 7, 2013

We've been pretty busy lately so this is slightly delayed. However, I do want to announce that Red Hat has joined the Google Cloud Platform Partner Program as a Technology Partner. Through this program, Red Hat and Google will collaborate on an open source community project known as JBoss CapeDwarf that increases the portability of Java-based Google App Engine applications and expands the deployment choices beyond Google’s cloud.

 

The JBoss CapeDwarf community project is an implementation of the Google App Engine Application Programming Interface (API) that enables applications to be deployed on either Red Hat JBoss Enterprise Application Platform (EAP) or its upstream application server project, WildFly, without modification. Red Hat JBoss EAP uses many of its enterprise-grade services such as authorization, transactions, data grid, and messaging to fulfill the Google App Engine API functionality in a way that is transparent to developers, users and the application.

 

The Google Cloud Platform offers a broad set of APIs for application development, cloud storage, large-scale computing, and big data. CapeDwarf leverages the Google App Engine on top of Red Hat JBoss EAP, regardless of whether it is deployed on premises or in an IaaS environment. Through the Red Hat product portfolio, developers have a path to run Google App Engine applications on a full enterprise-grade stack, using Red Hat JBoss EAP or combining it with Red Hat Enterprise Linux, OpenShift Enterprise, Red Hat CloudForms, or Red Hat Enterprise Virtualization.

 

CapeDwarf implements all the APIs as defined by Google App Engine for Java. The implementation serves as an integration layer between GAE APIs and services offered by JBoss EAP either out of the box or added by CapeDwarf itself. All data related APIs as well as others (Tasks APIs, Logging API) rely heavily on Infinispan, Hibernate Search, JGroups and Lucene, while the Tasks API also uses the HornetQ messaging system. The User API and the OAuth API rely on the Picket- link library.

 

Now of course you might ask why? Well ...

 

  • No more lock-in: Move your app from the Google cloud to CapeDwarf and back any time.
  • Google AppEngine on-premises: Now you have the option of initially deploying your app in your own CapeDwarf-based private cloud. When your app outgrows it, you’ll be able to simply migrate the app to Google’s Appspot.
  • Simple to create cluster: JBoss EAP makes it easy to run a multiple instances in a cluster. CapeDwarf has been implemented to support clustered environments from the start.
  • Easy debugging and multi-node testing: While the development server provided by Google App Engine can only be run in a singleserver configuration, CapeDwarf allows you to test your app on multiple nodes prior to uploading it to Google Appspot. Through remote debugging, you can also find those elusive bugs that do not show up when running the application on a single server.
  • Pure Java: CapeDwarf is written in pure Java and is universally portable.
  • Opensource: The complete CapeDwarf codebase is fully open sourced, which means you can fix any bugs you may find yourself, without waiting for the vendor to fix them.

 

You can deploy and run your Java App Engine applications on your own private RedHat’s OpenShift cloud: https://www.openshift.com/quickstarts/capedwarf

 

So go and give it a try. You'll also find that CapeDwarf offers access to many standard EE6 APIs that aren't available in vanilla GAE.

I wanted to write up my experiences at JUDCon, CamelOne and Summit last week. Then I remembered that I'd taken one or two photos, so what better way than to illustrate with a picture?

 

IMAG0027.jpgIMAG0036.jpg

 

Things got of to a great start on Sunday with the reception:

 

IMAG0037.jpg

 

I haven't got the final figures, but we had over 500 attendees at JUDCon and CamelOne, with many of the sessions standing-room only:

 

IMAG0041.jpg

On the first evening we had our usual dinner (pizza, salad and beer), podcast and lightning talks. However, this time we also were given the Best Application Server Award from ZeroTurnaround (thanks guys!):

 

IMAG0048.jpgIMG_0804.jpg

 

Then of course there was the traditional JBoss keynote. The team practiced and finalised the demo throughout the previous two days and did a fantastic job!

 

IMAG0050.jpg

 

We had over 1000 people in the room in the end, with many having to stand and watch, and almost as many people who couldn't get in (fire regulations):

 

IMG_0805.JPG

But fortunately it went over fairly straighforwardly in the end!

 

IMAG0055.jpgIMG_0812.JPGIMAG0058.jpg

 

And of course there was the traditional JBoss party, with the (becoming traditional) range of JBoss-themed drinks. I tried hard to sample each and every one of them on the night! I'm not sure if I accomplished this, because my only clear recollections are of discussion quantum mechanics and failure detection with James Strachan at the bar, using alcohol filled glasses to represent subatomic particles!

 

 

IMAG0063.jpgIMAG0064.jpg

 

In conclusion, I think all of the events went very well! The sessions I managed to attend were great and very vibrant. The sessions I was speaking at also seemed to be well received. So overall I'd say it was a success! Onward to next year and San Francisco!

Mark Little

EE7 launch announcement

Posted by Mark Little Jun 4, 2013

Java Enterprise Edition (Java EE) is truly a bedrock technology, serving as the global standard for enterprise application development.

 

The next release of Java's Enterprise Edition 7 raises the bar even higher for enterprise Java computing. RedHat has played a key role in this release as an active member of the Java development community including taking the lead in developing two new JSRs. 

 

To learn more, register today for the upcoming virtual launch event, planned for June 12, 2013.

 

Screen Shot 2013-06-04 at 13.53.46.png

 

RedHat development leads will provide overviews of their new JSRs in short breakout sessions during the upcoming launch. Pete Muir will give an overview of CDI 1.1 (JSR 346). Emmanuel Bernard, who took the lead in developing Bean Validation 1.1 (JSR 349), will also host a breakout session.

 

Attendees will learn about new ways to support increasing enterprise requirements; HTML 5 and dynamic, scalable applications; and a continued focus on developer productivity and technology integration.

 

Register  for the launch event today. Then come and hear from the experts about EE7 and come to Summit to hear where we think EE8 and beyond should be going.

Mark Little

JBUG Scotland

Posted by Mark Little May 10, 2013

I had the pleasure of speaking at the Scotland JBUG earlier this week in Edinburgh. It was a great event and well attended.

 

IMG_0748.jpg

I gave a presentation on our roadmaps for various products as well as some of the technical direction. There were a lot of good questions and the presentation should be uploaded soon.

Mark Little

EE7 is approved

Posted by Mark Little May 2, 2013

It's official, Java EE7 has been approved overwhelmingly. This is great news, particularly for the updates to various components such as CDI and JMS. I'm proud of our continued association with the JCP and glad to see that we could get this out relatively on time. Now it's on to EE8. Furthermore, given the WildFly announcement last week, we'll be looking to implement EE7 as soon as possible.

 

And now for the annoying and frustrating aspect: it seems like we have no vote recorded! Whether through a fault in the system (it's happened before), forgetfulness (it's happened before) or insanity (no comment!) we appear to have no vote associated with EE7 and some related JSRs. If this is our fault then it's my fault, since I had the token to vote. I'm chasing this with Oracle at the moment, because I'm sure we did vote! But according to the records that didn't happen. If it turns out we didn't vote then a big Mea Culpa to the team and our communities!

 

For the record: we would have/should have/did vote Yes/Approved to all of them.

Mark Little

And the winner is ...

Posted by Mark Little Apr 19, 2013

It's hard to believe that it was so many months ago that we announced the voting for the rename of JBossAS at Devoxx:

 

IMG_0624.jpg

At the time we had hoped to announce the name, but we had simply far more suggestions for names from the community than we ever expected. If we had been able to announce the winner, I had hoped to stand up there with a series of envelopes in a very Oscar-like manner and say things like "And the nominations were ...", of course with suitable drum rolls etc. Well it didn't happen at Devoxx and so we announced the nominations (without drums or music) and that we would make the final publication of the new name in early 2013 at a suitable conference or workshop.

 

Once the voting was completed and we had a name, the search was on for such a suitable conference and workshop. We had several options, but it seemed only right that we make the announcement about our most significant community project at our most significant community conference: JUDCon. As fate would have it, JUDCon Brazil (the very first time we will be in Brazil with JUDCon) was the first such conference after the votes were tallied. Therefore, we now had our name and our event, which meant I could put all of this together into a suitable keynote presentation. If you were there (or are there, depending upon when you view this article), you'll know that the runners up were jBeret in 3rd place and BaseJump in 2nd place. But the overall winner was ... (imagine a drum roll please) ...

 

wildfly_logo_600px.png

You'll see new domains, forums, JIRAs etc. associated with the project coming on line over the following hours and a presence on github imminently. I'd like to thank everyone who submitted names and voted. I'd also like to thank everyone who has helped to make this transition an overall positive thing for the community of users and developers. And finally I'd like to thank our design team for doing such a great job with the logo.

 

This announcement, along with the other one I made last month around free EAP binaries, are probably two of the most significant things to happen to the project in a long time. I expect to see us all build upon these changes and continue to ensure that WildFly remains the top open source application server for developers and deployers alike. We'll be making a lot of other announcements over the coming months around WildFly and several of our other projects and products, so watch out. You'll also start to see a few other changes around our community developer efforts and JBoss.org, but I won't spoil the surprise just yet!

Over the years as JBoss and then Red Hat, we've tried very hard to ensure that we work as an open organisation helping our communities. Whether you're a paying customer using the subscription to get great support, or an organisation/individual who doesn't need support (maybe because you can self support) you're all important to the wider success of JBoss and enterprise open source. Now prior to Red Hat, we at JBoss would support pretty much any combination of projects and their versions, as well as the cross-product combination. Of course that couldn't scale indefinitely and when we were acquired by Red Hat we moved to a more stable and scalable solution: the products would only be based on a very specific version of each project at a given point. I won't go into the details of how we take the projects and create the products but suffice it to say that there's a lot of work done by the development teams, QE, docs and of course productisation. This work goes into the up stream community projects but it can take a while for us to create new community binaries that benefit from it, due mainly to the effort we have to put in to supporting our customers, building other releases etc.

 

Now it should not come as a surprise that open source is core to everything we do and everyone we employ. It's in our blood and we will do a lot to ensure it continues to be a success. Sometimes we hear that the community is lagging behind the products, or that we're not as responsive as some might want us to be because of our product focus. What we really want to do is give the best possible experiences to our customers and our wider community, with the best Java middleware implementations around. Therefore, we've been thinking long and hard about the problem and how to resolve it. It's not easy and there are a number of ways to try to tackle it. However, there is one solution we've come up with that I think allows us to continue to provide the best products and support to our customers whilst at the same time ensuring that our communities are able to benefit too in a much more timely manner. It is this solution that I want to announce today.

 

What we are proposing to do is pretty simple: from the point where we start to productise the community project (e.g., AS7.1) we will release all product builds that we create as a result of this process into the community (e.g., EAP 6.0 Alpha 1, which is based on AS 7.1) so that all developers within our communities or with our customers can take advantage of them immediately. There will be no other community binaries for that major release of the community project after that point because the product builds are effectively a superset and we hope more beneficial to most developers. Of course community builds of the next major revision of the project will happen in parallel so you'll be able to contribute to and track those separately, so it's not a case of replacing community with product-only binaries. We're also changing the download processes and license for EAP so that it is as easy for developers to get hold of these bits as it is to get the community binaries. The net result is that everyone gets to experience the product whether or not they buy a full subscription with support. Now of course the value of the full subscription is much more than just the product binaries and support, and we all hope that people will want to migrate to a full subscription, but it's not going to be a requirement unless you want to put JBoss products into deployment. If you are a developer then you can use the same binaries as customers with this new subscription without having to worry about evaluation periods, or missing critical bug fixes.

 

I believe this is a great step in the evolution of JBoss/Red Hat and enterprise open source in general. We're continually breaking down barriers to adoption of open source and enterprise middleware, whether by making EE6 much more easily consumable via approaches such as AS7 and CDI, or pushing into new communities with efforts such as TorqueBox or Immutant. With this change that I have announced, we're now removing another barrier by ensuring that all of our communities can get access to our product releases!

 

Onward!

Filter Blog

By date:
By tag: