Abstract: Historically, the term “Hadoop” has been considered synonymous with its core technologies: MapReduce and the Hadoop Distributed File System (HDFS). But today the definition of Hadoop is rapidly evolving.
The Hadoop community is generalizing the application runtime model beyond MapReduce. On the storage front, we’re seeing the emergence of many alternative Hadoop-compatible file systems. Red Hat has built an interface layer for its Red Hat Storage Server product. This complete implementation of the Hadoop file system interface lets Hadoop-related projects run transparently, directly on a Red Hat Storage Server cluster. (more…)
abstract: The world is moving fast. Is your IT team keeping up? Are you able to deliver the new applications and services that the business and your customers are demanding? The old ways of doing application development and deliver are falling behind as the world zooms by. Waterfall development and departmental silos are rapidly becoming boat anchors for IT. (more…)
For more information about Red Hat OpenShift and other related topics, visit:
As a Red Hat UX designer who is visible in the open source community, I often receive requests for advice from developers looking for help in improving their apps’ user experience. Here are five tips from that experience that you can put to work on your own:
1. Prioritize for the best impact
Not every user is going to use every feature of your software, but some features almost every user will use. Not every user who uses a given feature is going to use it frequently, but some users will use that feature all of the time. Take a look at the grid below:
In previous articles we mentioned tips on how to package collections, but we never wrote about initscripts, which are one reason why daemons are harder to package as a collection.
I’ve picked a short(er) initscript to show what has to be modified if you want to run your initscript in a collection. Below is the diff between the mongodb initscript and collection version of the mongodb initscript. Currently, logfiles, pidfiles and configuration files are stored mostly as in the example below, but it depends on the packager. One needs to check where daemon, configuration etc. has been installed and change the initscript accordingly. This example shows generic changes.
For more information about Red Hat Software Collections or Red Hat Developer Toolset, visit developer.redhat.com/RHEL.
This year Akademy, the KDE conference, will be held in Brno very close to the Red Hat office at the University (FEKT VUT) in the technological park. There will be many KDE related presentations and workshops. I’m looking forward to hearing about new features of KF5 (KDE Frameworks) and Plasma.