IBM/Red Hat/Fedora Leftovers

-
5 steps to migrate your application to containers | Opensource.com
Generally, you consider it a good thing when people want to use your application. However, when the application runs on a server, there's a cost for popularity. With users come increased demands on resources, and at some point, you may find that you need to scale your app. One option is to throw more servers at the problem, establish a load balancer like Nginx, and let the demand sort itself out. That option can be expensive, though, because there are no savings when demand is low, and you're running instances of your app on servers devoid of traffic. Containers have the advantage of being ephemeral, launching when new instances are available and fading away with decreased demand. If that sounds like a feature you need, then it may be time to migrate your app to containers.
Migrating an app to a container can quickly become disorienting. While the environment within a container may feel familiar, many container images are minimal, and they are designed to be stateless. In a way, though, this is one of the strengths of containers. Like a Python virtual environment, it's a blank slate that lets you build (or rebuild) your application without the invisible defaults that many other environments provide.
-
My tips for maintaining dotfiles in source control | Opensource.com
Ever started using a new computer, by choice or because the old one let the magic smoke out, and got frustrated at how long it took to get everything just right? Even worse, ever spent some time reconfiguring your shell prompt, then realizing you liked it better before?
This problem, for me, became acute when I decided I wanted to do development in containers. Containers are ephemeral. The development tooling is easy to solve: A container image with the tooling works. The source code is easy to solve: Source control maintains it, and development happens on branches. But if every time I create a container, I need to configure it carefully—that's going to be a pain.
-
Fedora Linux 37 development schedule – Fedora Community Blog
Fedora Linux 36 branches from Rawhide today. While there’s still a lot of work before the Fedora Linux 36 release in April, this marks the beginning of the Fedora Linux 37 development cycle. The work you do in Rawhide will be in the Fedora Linux 37 release in October.
-
What can video games teach us about edge computing?
This post was inspired by a Compiler episode on the same topic. Compiler is a Red Hat podcast about all the things you’ve always wanted to know about what moves tech forward, straight from the people who know it best. Check it out!
Let’s say you’re playing your favorite online multiplayer game when—all of a sudden—things start getting choppy. Your character isn’t moving, other players start freezing up, maybe the in-game music isn’t even coming through.
-
Automate and deploy a JBoss EAP cluster with Ansible | Red Hat Developer
In my series introducing WildFly server configuration with Ansible collection for JCliff, I described how developers can use Ansible to manage a standalone Red Hat JBoss Enterprise Application Platform (JBoss EAP) instance. I've also written about using Ansible to automate Apache Tomcat and Red Hat JBoss Web Server deployments. In this article, we'll go a bit deeper and use Ansible to deploy a fully operational cluster of JBoss EAP instances. I'll show you how to automate the setup of each JBoss EAP instance and how to configure the network requirements—notably, fault tolerance and high availability—using features provided by the WildFly Ansible collection.
-
5 technical debt lessons the pandemic taught IT leaders | The Enterprisers Project
Veteran IT leaders have long understood the impact technical debt has on an organization’s digital transformation and ability to respond rapidly to changing demands. The global pandemic underscored that understanding. Technical debt can create talent, speed, reliability, and scalability issues for organizations in the best of times – and the worst.
Beyond confirming the burden of technical debt, the impact of the pandemic has been mixed. In some cases, IT organizations may have gotten the go-ahead to address some technical debt that may have hindered the enterprise’s ability to pivot. In others, IT functions had to make short-term decisions to enable remote work, new digital commerce solutions, or supply chain fixes that increased their technical debt.
-

- Login or register to post comments
Printer-friendly version- 2262 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is released
After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release.
|
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future Tech
The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world.
Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility.
|
today's howtos
|








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

Recent comments
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago