From hobbyist SoC devices such as the ubiquitous Raspberry Pi to a complete domination of the mobile device market, ARM processors have proven the value of the architecture. It is easy to see why ARM processors were able to explode in this market, given that they are able to pack quite a bit of performance into a rather small physical space. Take for instance Qualcomm’s Snapdragon 400 processor, which is used in many products including the Huawei Watch This processor provides a dual core, fast, performance using 14-nanometer design. This makes it small enough to fit on your wrist, and it is efficient enough to limit power consumption enough to run on a battery, which can also fit on your wrist. The usefulness in these spheres of ARM processors is well known, and the fact that RHEL seems to have little interest in the mobile, embedded device, or hobbyist market is also fairly well known. What should be of interest to Red Hat developers, though, is the potential for the Enterprise Server market that ARM processors seem to be displaying. While x86 devices likely are to remain in place for workstations and laptops, the low power usage and small physical design of ARM processors make it interesting to the server market, where power consumption and space are also limitations.
Continue reading “After Years of Linux on ARM, when is the Year of Red Hat on ARM servers?”
An RHMAP Environment provides a Node.js runtime for Mobile Backends. There are 2 environment types: Dynofarm & OpenShift. The former is an LXC based PaaS, written in Node.js & bash. It is superseded by OpenShift environments. However, there are still many Dynofarm environments in use in the RHMAP SaaS offering.
One of the biggest challenges for developers to build mobile applications is data synchronization. It’s the foundation for many different types of mobile applications, but it’s very complicated and very hard to implement.