Sign In
Sign In

Best Backend Frameworks for Web Development in 2025

Best Backend Frameworks for Web Development in 2025
Hostman Team
Technical writer
Infrastructure

Frameworks simplify development, eliminate chaos, and provide a clear structure when building an application.

Each framework comes with a specific set of ready-made tools—battle-tested technical solutions that accelerate and simplify development.

In this article, we’ll take a look at the 10 most popular backend frameworks for 2025—essential tools for nearly every modern application.

Server Framework Tasks

Typically, any server-side application performs a set of standard functions:

  • Routing. Handling user requests via a REST API.
  • Authentication. Managing user registration and login.
  • Logic. Implementing the core server logic: generating page content, managing carts, handling messages, etc.
  • Storage. Connecting to a (remote) database to write, read, and sort data.
  • Payments. Processing payment transactions.
  • Extensions. Supporting third-party software (libraries and frameworks) required for managing external devices: smartphones, personal computers, servers, etc.
  • Microservices. Communicating with remote applications (such as microservices) via REST API.

A good backend framework should satisfy all the above requirements, ensuring functionality, security, and performance in the final product.

1. ASP.NET Core

ASP.NET Core is a cross-platform framework developed by Microsoft for building modern web applications and APIs. It works with the C# programming language and runs on Windows, Linux, and macOS.

Importantly, ASP.NET Core is not the same as ASP.NET Framework. It is its evolutionary successor: a modern, modular, cross-platform solution.

6762631c Ea20 4e85 B5f4 838a83643f77

The framework uses the classic MVC (Model-View-Controller) design pattern to separate data and logic, dividing the application into three parts: Model, View, and Controller.

Details

  • Programming Language: C#
  • Developer: Microsoft
  • First Release: 2016

Features

  • Cross-platform. Enables development and deployment on most popular operating systems: Windows, Linux, macOS.
  • Performance. Optimized for high performance and scalability, allowing apps to handle large numbers of requests.
  • Modularity. Uses only the necessary components, making the application lightweight and flexible.
  • Support. Actively maintained and updated by Microsoft, ensuring access to new features, bug fixes, and security improvements.
  • Tooling. Integrates with modern development tools like Visual Studio and Visual Studio Code.

Audience

Thanks to its flexibility, ASP.NET Core is suitable not only for web development with its client-side services but also for mobile apps and games that require complex backend logic and fast database interactions.

However, despite its cross-platform nature, ASP.NET Core remains more focused on Windows developers and users.

The framework is especially beneficial for large enterprises and corporate developers who need to build scalable, high-performance, and fault-tolerant applications and microservices with a clear and strict architecture.

Code

Example of a basic routing setup in ASP.NET Core using the MVC template:

Model:

app.UseEndpoints(endpoints =>
{
	endpoints.MapControllerRoute(
		name: "default",
		pattern: "{controller=Home}/{action=Index}/{id?}");
});

Controller:

public class BooksController : Controller
{
	public IActionResult Details(int id)
	{
		ViewBag.Id = id;
		return View();
	}
}

View:

@{
	ViewData["Title"] = "Details";
	int id = ViewBag.Id;
}

<h1>Details</h1>
Book Id : @id

2. Django

Django is a free, high-level framework written in Python that also follows the MVC design pattern.

It’s a modular framework that heavily emphasizes the “Don’t Repeat Yourself” (DRY) principle, which helps reduce code redundancy and simplify maintenance.

Each Django project consists of multiple apps that can be developed and tested independently. This allows for easy reuse across different projects.

A key feature of the framework is its Object-Relational Mapping (ORM) tool, which allows developers to manage relational databases using only Python code—no SQL required.

Details

  • Programming Language: Python
  • Developer: Django Software Foundation
  • First Release: 2005

Features

  • Reusability. The modular architecture makes it easy to reuse code and avoid duplication.
  • Tools. Has a broad set of built-in features: authentication system, admin panel, router, database manager, etc.
  • Support. Offers well-structured documentation and has a large developer community actively contributing and solving common issues.

Audience

Thanks to its built-in tools and modularity, Django is ideal for quickly creating and deploying MVPs (Minimum Viable Products).

This makes it a great choice for startups and small businesses.

At the same time, Django is also scalable enough to support enterprise-level solutions.

Code

A snippet of Django code for routing user requests:

from rest_framework import routers
from collaborativeAPP import views

router = routers.DefaultRouter()

router.register(r'get_one', views.OneViewSet)
router.register(r'get_two', views.TwoViewSet)
router.register(r'get_three', views.ThreeViewSet)

urlpatterns = patterns(
	...
	url(r'^service/', include(router.urls))
)

3. Laravel

Laravel is a popular PHP framework for building web applications that follows the MVC design pattern.

It’s known for its clear syntax, the Blade templating engine, and the built-in task automation tool Artisan CLI.

Laravel simplifies routine tasks, speeds up development, and delivers high application performance.

It is supported by a large community and has extensive documentation, making it an accessible tool for modern web development.

Details

  • Programming Language: PHP
  • Developer: Taylor Otwell + Community
  • First Release: 2011

Features

  • Syntax. Known for its high-level abstractions and clean, expressive syntax that simplifies writing and reading code, even for beginners.
  • Templating. Has a built-in templating system that allows developers to create dynamic pages using powerful yet simple syntax.
  • Community. Backed by a large and active developer community creating additional packages for the framework.

Audience

Laravel’s concise syntax is especially useful for beginner PHP developers and freelancers looking to enhance their projects with more functionality.

Its simplicity and expressiveness also make it a popular choice in educational programs for teaching web development.

Startup developers can also quickly test ideas and hypotheses using Laravel.

Code

A basic example of routing syntax in Laravel:

Route::match(array('GET', 'POST'), '/', function()
{
    return 'Main Page';
});

Route::post('foo/bar', function()
{
    return 'Foo and Bar';
});

Route::get('user/{id}', function($id)
{
    return 'User '.$id;
});

4. Ruby on Rails

Ruby on Rails (or simply Rails) is a popular web development framework written in Ruby that provides a ready-made structure for writing code. 

Its main feature is the “Convention over Configuration” principle, which radically changes the way web apps are developed by making it more intuitive and productive. 

Instead of requiring developers to write extensive config files, Rails assumes sensible defaults, significantly reducing the amount of code needed.

Details

  • Programming Language: Ruby
  • Developer: David Heinemeier Hansson
  • First Release: 2004

Features

  • Speed. With standardized conventions, developers can quickly start building functionality without extensive setup.
  • Standardization. In addition to speeding up development, defaults make code easier to read and maintain, especially in teams
  • Security. Includes built-in security features like protection against SQL injection, XSS, CSRF attacks, and more.

Audience

The main draw of Ruby on Rails is development speed. It’s perfect for those who need to rapidly prototype and validate new features.

Sometimes, using an off-the-shelf CMS can either overcomplicate or limit your project’s flexibility. In such cases, Rails lets you easily build a custom engine for your web app with minimal effort.

Code

A simple example of a Rails controller for displaying articles:

class ArticlesController < ApplicationController
	def index
		@articles = Article.recent
	end

	def show
		@article = Article.find(params[:id])
		fresh_when etag: @article
	end

	def create
		article = Article.create!(article_params)
		redirect_to article
	end

	private
		def article_params
			params.require(:article).permit(:title, :content)
		end
end

5. Express.js

Express.js is the most popular (and possibly the best overall backend framework) minimalist web framework on the Node.js platform, used to create flexible HTTP servers using RESTful APIs.

It's a powerful tool that suits a wide range of developers due to its simplicity and vast ecosystem.

Details

  • Programming language: JavaScript
  • Developer: StrongLoop and IBM
  • First release: 2010

Features

  • Conciseness: Simple and clear syntax in JavaScript.
  • Flexibility: The framework does not enforce a strict project structure, allowing developers to design their own application architecture.
  • Isomorphism: With Express.js, it’s possible to use JavaScript both on the client (browser) and server side (Node.js), unifying the stack.
  • Libraries: Being built on Node.js, Express.js gives access to tens of thousands of useful server-side packages for tasks like data serialization, math operations, database writing, network connection handling, etc. All written in JavaScript.
  • Proven reliability: Despite many modern alternatives, Express.js has years of support and is considered a classic, well-polished option.

Audience

Beginner Node.js developers should absolutely get familiar with Express.js as it's used in 9 out of 10 web projects.

Since it's written in JavaScript, it's an excellent gateway to backend development for frontend developers looking to build full-stack apps.

For RESTful API developers, Express.js is a must-have.

Due to its popularity and reliability, many consider it the only true JavaScript backend framework.

Code

The simplest Express.js app looks like this:

const express = require('express')
const app = express()
const port = 3000

app.get('/', (req, res) => {
	res.send('Welcome!')
})

app.listen(port, () => {
	console.log(`App is listening on port ${port}`)
})

6. CakePHP

CakePHP is an open-source framework for PHP web development based on the MVC architecture.

Originally designed as a PHP clone of Ruby on Rails, it adopted many of its ideas:

  • Custom file structure
  • Plugin-based extensibility
  • Data abstraction tools
  • Support for numerous databases

Details

  • Programming language: PHP
  • Developer: Cake Software Foundation
  • First release: 2005

Features

  • Code generation: The Bake tool quickly creates model, controller, and view skeletons, speeding up development.
  • Structure: The framework assumes a predefined file/class directory structure. If followed, it automatically loads needed files with no extra setup.
  • Auto-routing: It automatically connects URLs to the corresponding controllers/actions, simplifying route creation.

Audience

CakePHP is quite versatile—suitable for both startups and large enterprises. However, its wide range of tools might require beginners to spend time learning.

Code

Example controller from the official documentation:

namespace App\Controller;

class ArticlesController extends AppController
{
	public function index()
	{
		$this->loadComponent('Paginator');
		$articles = $this->Paginator->paginate($this->Articles->find());
		$this->set(compact('articles'));
	}
}

7. Flask

Flask is an extremely lightweight Python backend framework perfect for building small to medium-sized web apps. Simplicity and minimalism are its trademarks—it offers just the essentials for web development, while remaining flexible and versatile.

Details

  • Programming language: Python
  • Developer: Armin Ronacher
  • First release: 2010

Features

  • Compactness: Lightweight and fast, with no unnecessary components, making it very easy to learn.
  • Flexibility: Does not impose a specific structure, allowing diverse architectural approaches.

Audience

Flask is ideal for small projects and feature-testing prototypes. It’s a great entry point into Python web development for beginners. Even as a hobby project grows into a complex commercial app, Flask’s flexibility and scalability can support the transition.

Code

Here’s a simple app with a router that renders content:

from flask import Flask, render_template

app = Flask(__name__)

@app.route('/')
def index():
	return render_template('index.html')

@app.route('/about')
def about():
	return render_template('about.html')

8. Spring Boot

Spring Boot is a powerful Java backend framework built on top of the lower-level Spring framework. It is part of the Spring ecosystem and provides tools that streamline and accelerate development. While Spring itself requires complex manual configuration, Spring Boot simplifies this through auto-configuration and ready-made templates.

Details

  • Programming language: Java
  • Developer: Rod Johnson, VMware
  • First release: 2014

Features

  • Auto-configuration: Automatically configures based on defined dependencies, reducing the need for extensive config files.
  • Built-in servers: Includes embedded servers like Tomcat, Jetty, and Undertow, allowing apps to run directly from the IDE or CLI.

Audience

Ideal for beginners exploring the Spring ecosystem—it makes learning much easier. Great for building microservices due to fast deployment of individual app components. Also plays well with Docker and orchestration systems like Kubernetes.

Code

A basic Spring Boot app from the official docs:

package com.example.springboot;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class HelloController {
	@GetMapping("/")
	public String index() {
		return "Greetings from Spring Boot!";
	}
}

9. Koa

Koa is a modern web framework for Node.js created by the same team behind Express.js. Naturally, it's written in JavaScript. Koa can be seen as a more expressive, minimalist, and flexible iteration of Express.js, removing many of its limitations and complexities.

Details

  • Programming language: JavaScript
  • Developer: StrongLoop
  • First release: 2017

Features

  • Async-first: Designed for async/await from the ground up, making asynchronous code cleaner and more maintainable compared to traditional callbacks.
  • Lightweight: Ships with no built-in middleware, so developers can pick and choose exactly what they need.

Code

A basic Koa app:

'use strict';

const Koa = require('koa');
const app = new Koa();

app.use(ctx => {
	ctx.body = 'Hello, Timeweb';
});

app.listen(3000);

10. Phoenix

Phoenix is a modern web framework for the functional programming language Elixir.

  • Programming language: Elixir
  • Developer: Phoenix Framework
  • First release: 2014

Features

  • Performance: Uses Elixir and the Erlang VM, offering high performance and scalability via functional programming and concurrency.
  • Clean code: Elixir's functional nature encourages clean, predictable, and maintainable code.

Audience

Best suited for developers who prefer functional programming, immutable data, and pure functions. It is also a great tool for Erlang developers who want to build web apps using familiar principles.

Code

A basic Phoenix router from the official docs:

defmodule HelloWeb.Router do
	use HelloWeb, :router

	pipeline :browser do	
		plug :accepts, ["html"]
		plug :fetch_session
		plug :fetch_live_flash
		plug :put_root_layout, html: {HelloWeb.Layouts, :root}
		plug :protect_from_forgery
		plug :put_secure_browser_headers
	end

	pipeline :api do
		plug :accepts, ["json"]
	end

	scope "/", HelloWeb do
		pipe_through :browser
		get "/", PageController, :home
	end
end

Conclusion

We've looked at the most popular and well-established backend frameworks developers have relied on for years, and continue to rely on in 2025. Many of these frameworks are over 15 years old, which is a strong indicator of their maturity and suitability for various projects. They’ve all gone through numerous updates over time, adapting to technological changes and evolving developer needs. Their stability and robustness ensure they remain go-to tools for building modern applications.

Infrastructure

Similar

Infrastructure

Virtualization vs Containerization: What They Are and When to Use Each

This article explores two popular technologies for abstracting physical hardware: virtualization and containerization. We will provide a general overview of each and also discuss the differences between virtualization and containerization. What Is Virtualization The core component of this technology is the virtual machine (VM). A VM is an isolated software environment that emulates the hardware of a specific platform. In other words, a VM is an abstraction that allows a single physical server to be transformed into multiple virtual ones. Creating a VM makes sense when you need to manage all operating system kernel settings. This avoids kernel conflicts with hardware, supports more features than a specific OS build might provide, and allows you to optimize and install systems with a modified kernel. What Is Containerization Containers work differently: to install and run a container platform, a pre-installed operating system kernel is required (this can also be on a virtual OS). The OS allocates system resources for the containers that provide a fully configured environment for deploying applications. Like virtual machines, containers can be easily moved between servers and provide a certain level of isolation. However, to deploy them successfully, it’s sufficient for the base kernel (e.g., Linux, Windows, or macOS) to match — the specific OS version doesn’t matter. Thus, containers serve as a bridge between the system kernel layer and the application layer. What Is the Difference Between Containerization and Virtualization Some, especially IT beginners, often frame it as "virtualization vs containerization." But these technologies shouldn't be pitted against each other — they actually complement one another. Let’s examine how they differ and where they overlap by looking at how both technologies perform specific functions. Isolation and Security Virtualization makes it possible to fully isolate a VM from the rest of the server, including other VMs. Therefore, VMs are useful when you need to separate your applications from others located on the same servers or within the same cluster. VMs also increase the level of network security. Containerization provides a certain level of isolation, too, but containers are not as robust when it comes to boundary security compared to VMs. However, solutions exist that allow individual containers to be isolated within VMs — one such solution is Hyper-V. Working with the Operating System A VM is essentially a full-fledged OS with its own kernel, which is convenient but imposes high demands on hardware resources (RAM, storage, CPU). Containerization uses only a small fraction of system resources, especially with adapted containers. When forming images in a hypervisor, the minimal necessary software environment is created to ensure the container runs on an OS with a particular kernel. Thus, containerization is much more resource-efficient. OS Updates With virtualization, you have to download and install OS updates on each VM. To install a new OS version, you need to update the VM — in some cases, even create a new one. This consumes a significant amount of time, especially when many virtual machines are deployed. With containers, the situation is similar. First, you modify a file (called a Dockerfile) that contains information about the image. You change the lines that specify the OS version. Then the image is rebuilt and pushed to a registry. But that’s not all: the image must then be redeployed. To do this, you use orchestrators — platforms for managing and scaling containers. Orchestration tools (the most well-known are Kubernetes and Docker Swarm) allow automation of these procedures, but developers must install and learn them first. Deployment Mechanisms To deploy a single VM, Windows (or Linux) tools will suffice, as will the previously mentioned Hyper-V. But if you have two or more VMs, it’s more convenient to use solutions like PowerShell. Single containers are deployed from images via a hypervisor (such as Docker), but for mass deployment, orchestration platforms are essential. So in terms of deployment mechanisms, virtualization and containerization are similar: different tools are used depending on how many entities are being deployed. Data Storage Features With virtualization, VHDs are used when organizing local storage for a single VM. If there are multiple VMs or servers, the SMB protocol is used for shared file access. Hypervisors for containers have their own storage tools. For example, Docker has a local Registry repository that lets you create private storage and track image versions. There is also the public Docker Hub repository, which is used for integration with GitHub. Orchestration platforms offer similar tools: for instance, Kubernetes can set up file storage using Azure’s infrastructure. Load Balancing To balance the load between VMs, they are moved between servers or even clusters, selecting the one with the best fault tolerance. Containers are balanced differently. They can’t be moved per se, but orchestrators provide automatic starting or stopping of individual containers or whole groups. This enables flexible load distribution between cluster nodes. Fault Tolerance Faults are also handled in similar ways. If an individual VM fails, it’s not difficult to transfer that VM to another server and restart the OS there. If there’s an issue with the server hosting the containerization platform, containers can be quickly recreated on another server using the orchestrator. Pros and Cons of Virtualization Advantages: Reliable isolation. Logical VM isolation means failures in one VM don’t affect the others on the same server. VMs also offer a good level of network security: if one VM is compromised, its isolation prevents infection of others. Resource optimization. Several VMs can be deployed on one server, saving on purchasing additional hardware. This also facilitates the creation of clusters in data centers. Flexibility and load balancing. VMs are easily transferred, making it simpler to boost cluster performance and maintain systems. VMs can also be copied and restored from backups. Furthermore, different VMs can run different OSs, and the kernel can be any type — Linux, Windows, or macOS — all on the same server. Disadvantages: Resource consumption. VMs can be several gigabytes in size and consume significant CPU power. There are also limits on how many VMs can run on a single server. Sluggishness. Deployment time depends on how "heavy" the VM is. More importantly, VMs are not well-suited to scaling. Using VMs for short-term computing tasks is usually not worthwhile. Licensing issues. Although licensing is less relevant for Russian developers, you still need to consider OS and software licensing costs when deploying VMs — and these can add up significantly in a large infrastructure. Pros and Cons of Containerization Advantages: Minimal resource use. Since all containers share the same OS kernel, much less hardware is needed than with virtual machines. This means you can create far more containers on the same system. Performance. Small image sizes mean containers are deployed and destroyed much faster than virtual machines. This makes containers ideal for developers handling short-term tasks and dynamic scaling. Immutable images. Unlike virtual machines, container images are immutable. This allows the launch of any number of identical containers, simplifying testing. Updating containers is also easy — a new image with updated contents is created on the container platform. Disadvantages: Compatibility issues. Containers created in one hypervisor (like Docker) may not work elsewhere. Problems also arise with orchestrators: for example, Docker Swarm may not work properly with OpenShift, unlike Kubernetes. Developers need to carefully choose their tools. Limited lifecycle. While persistent container storage is possible, special tools (like Docker Data Volumes) are required. Otherwise, once a container is deleted, all its data disappears. You must plan ahead for data backup. Application size. Containers are designed for microservices and app components. Heavy containers, such as full-featured enterprise software, can cause deployment and performance issues. Conclusion Having explored the features of virtualization and containerization, we can draw a logical conclusion: each technology is suited to different tasks. Containers are fast and efficient, use minimal hardware resources, and are ideal for developers working with microservices architecture and application components. Virtual machines are full-fledged OS environments, suitable for secure corporate software deployment. Therefore, these technologies do not compete — they complement each other.
10 June 2025 · 7 min to read
Infrastructure

Top RDP Clients for Linux in 2025: Remote Access Tools for Every Use Case

RDP (Remote Desktop Protocol) is a proprietary protocol for accessing a remote desktop. All modern Windows operating systems have it by default. However, a Linux system with a graphical interface and the xrdp package installed can also act as a server. This article focuses on Linux RDP clients and the basic principles of how the protocol works. Remote Desktop Protocol RDP operates at the application layer of the OSI model and is based on the Transport Layer Protocol (TCP). Its operation follows this process: A connection is established using TCP at the transport layer. An RDP session is initialized. The RDP client authenticates, and data transmission parameters are negotiated. A remote session is launched: the RDP client takes control of the server. The server is the computer being remotely accessed. The RDP client is the application on the computer used to initiate the connection. During the session, all computational tasks are handled by the server. The RDP client receives the graphical interface of the server's OS, which is controlled using input devices. The graphical interface may be transmitted as a full graphical copy or as graphical primitives (rectangles, circles, text, etc.) to save bandwidth. By default, RDP uses port 3389, but this can be changed if necessary. A typical use case is managing a Windows remote desktop from a Linux system. From anywhere in the world, you can connect to it via the internet and work without worrying about the performance of the RDP client. Originally, RDP was introduced in Windows NT 4.0. It comes preinstalled in all modern versions of Windows. However, implementing a Linux remote desktop solution requires special software. RDP Security Two methods are used to ensure the security of an RDP session: internal and external. Standard RDP Security: This is an internal security subsystem. The server generates RSA keys and a public key certificate. When connecting, the RDP client receives these. If confirmed, authentication takes place. Enhanced RDP Security: This uses external tools to secure the session, such as TLS encryption. Advantages of RDP RDP is network-friendly: it can work over NAT, TCP, or UDP, supports port forwarding, and is resilient to connection drops. Requires only 300–500 Kbps bandwidth. A powerful server can run demanding apps even on weak RDP clients. Supports Linux RDP connections to Windows. Disadvantages of RDP Applications sensitive to latency, like games or video streaming, may not perform well. Requires a stable server. File and document transfer between the client and server may be complicated due to internet speed limitations. Configuring an RDP Server on Windows The most common RDP use case is connecting to a Windows server from another system, such as a Linux client. To enable remote access, the target system must be configured correctly. The setup is fairly simple and works "out of the box" on most modern Windows editions.  Enable remote desktop access via the Remote Access tab in System Properties. Select the users who can connect (by default, only administrators). Check firewall settings. Some profiles like “Public” or “Private” may block RDP by default. If the server is not in a domain, RDP might not work until you allow it manually via Windows Firewall → Allowed Apps. If behind a router, you might need to configure port forwarding via the router’s web interface (typically under Port Forwarding). Recall that RDP uses TCP port 3389 by default. Best RDP Clients for Linux Remmina Website: remmina.org Remmina is a remote desktop client with a graphical interface, written in GTK+ and licensed under GPL. In addition to RDP, it supports VNC, NX, XDMCP, SPICE, X2Go, and SSH. One of its key features is extensibility via plugins. By default, RDP is not available until you install the freerdp plugin. After installing the plugin, restart Remmina, and RDP will appear in the menu. To connect: Add a new connection. Fill in connection settings (you only need the remote machine's username and IP). Customize further if needed (bandwidth, background, hotkeys, themes, etc.). Save the connection — now you can connect with two clicks from the main menu. If you need to run Remmina on Windows, a guide is available on the official website. FreeRDP Website: freerdp.com FreeRDP is a fork of the now-unsupported rdesktop project and is actively maintained under the Apache license. FreeRDP is a terminal-based client. It is configured and launched entirely via the command line. Its command structure is similar to rdesktop, for example: xfreerdp -u USERNAME -p PASSWORD -g WIDTHxHEIGHT IP This command connects to the server at the given IP using the specified credentials and screen resolution. KRDC Website: krdc KRDC (KDE Remote Desktop Client) is the official remote desktop client for KDE that supports RDP and VNC protocols. It offers a clean and straightforward interface consistent with KDE's Plasma desktop environment. KRDC is ideal for users of KDE-based distributions like Kubuntu, openSUSE KDE, and Fedora KDE Spin. It integrates well with KDE's network tools and provides essential features such as full-screen mode, session bookmarking, and network browsing via Zeroconf/Bonjour. KRDC is actively maintained by the KDE community and is available through most Linux package managers. GNOME Connections Website: gnome-connections Vinagre was the former GNOME desktop's default remote desktop client. GNOME Connections, a modernized remote desktop tool for GNOME environments, has since replaced it. GNOME Connections supports RDP and VNC, providing a simple and user-friendly interface that matches the GNOME design language. It focuses on ease of use rather than configurability, making it ideal for non-technical users or quick access needs. Features: Bookmarking for quick reconnections Simple RDP session management Seamless integration into GNOME Shell Connections is maintained as part of the official GNOME project and is available in most distribution repositories. Apache Guacamole Website: guacamole.apache.org This is the simplest yet most complex remote desktop software for Linux. Simple because it works directly in a browser — no additional programs or services are needed. Complex because it requires one-time server installation and configuration. Apache Guacamole is a client gateway for remote connections that works over HTML5. It supports Telnet, SSH, VNC, and RDP — all accessible via a web interface. Although the documentation is extensive, many ready-made scripts exist online to simplify basic setup. To install: wget https://git.io/fxZq5 -O guac-install.sh chmod +x guac-install.sh ./guac-install.sh After installation, the script will provide a connection address and password. To connect to a Windows server via RDP: Open the Admin Panel, go to Settings → Connections, and create a new connection. Enter the username and IP address of the target machine — that's all you need. The connection will now appear on the main page, ready for use. Conclusion RDP is a convenient tool for connecting to a remote machine running Windows or a Linux system with a GUI. The server requires minimal setup — just a few settings and firewall adjustments — and the variety of client programs offers something for everyone.
09 June 2025 · 6 min to read
Infrastructure

Docker Container Storage and Registries: How to Store, Manage, and Secure Your Images

Docker containerization offers many benefits, one of which is image layering, enabling fast container generation. However, containers have limitations — for instance, persistent data needs careful planning, as all data within a container is lost when it's destroyed. In this article, we’ll look at how to solve this issue using Docker’s native solution called Docker Volumes, which allows the creation of persistent Docker container storage. What Happens to Data Written Inside a Container To begin, let’s open a shell inside a container using the following command: docker run -it --rm busybox Now let’s try writing some data to the container: echo "Hostman" > /tmp/data cat /tmp/data Hostman We can see that the data is written, but where exactly? If you're familiar with Docker, you might know that images are structured like onions — layers stacked on top of each other, with the final layer finalizing the image. Each layer can only be written once and becomes read-only afterward. When a container is created, Docker adds another layer for handling write operations. Since container lifespans are limited, all data disappears once the container is gone. This can be a serious problem if the container holds valuable information. To solve this, Docker provides a solution called Docker Volumes. Let’s look at what it is and how it works. Docker Volumes Docker Volumes provide developers with persistent storage for containers. This tool decouples data from the container’s lifecycle, allowing access to container data at any time. As a result, data written inside containers remains available even after the container is destroyed, and it can be reused by other containers. This is a useful solution for sharing data between Docker containers and also enables new containers to connect to the existing storage. How Docker Volumes Work A directory is created on the server and then mounted into one or more containers. This directory is independent because it is not included in the Docker image layer structure, which allows it to bypass the read-only restriction of the image layers for containers that include such a directory. To create a volume, use the following command: docker volume create Now, let’s check its location using: docker volume inspect volume_name The volume name usually consists of a long alphanumeric string. In response, Docker will display information such as the time the volume was created and other metadata, including the Mountpoint. This line shows the path to the volume. To view the data stored in the volume, simply open the specified directory. There are also other ways to create a Docker Volume. For example, the -v option can be added directly during container startup, allowing you to create a volume on the fly: docker run -it --rm -v newdata:/data busybox Let’s break down what’s happening here: The -v argument follows a specific syntax, indicated by the colon right after the volume name (in this case, we chose a very creative name, newdata). After the colon, the mount path inside the container is specified. Now, you can write data to this path, for example: echo "Cloud" > /data/cloud Data written this way can easily be found at the mount path. As seen in the example above, the volume name is not arbitrary — it matches the name we provided using -v. However, Docker Volumes also allow for randomly generated names, which are always unique to each host. If you’re assigning names manually, make sure they are also unique. Now, run the command: docker volume ls If the volume appears in the list, it means any number of other containers can use it. To test this, you can run: docker run -it --rm -v newdata:/data busybox Then write something to the volume. Next, start another container using the exact same command and you’ll see that the data is still there and accessible — meaning it can be reused. Docker Volumes in Practice Now let’s take a look at how Docker Volumes can be used in practice. Suppose we're developing an application to collect specific types of data — let’s say football statistics. We gather this data and plan to use it later for analysis — for example, to assess players’ transfer market values or for betting predictions. Let’s call our application FootballStats. Preserving Data After Container Removal Obviously, if we don’t use Docker Volumes, all the collected statistics will simply be lost as soon as the container that stored them is destroyed. Therefore, we need to store the data in volumes so it can be reused later. To do this, we use the familiar -v option:  -v footballstats:/dir/footballstats This will allow us to store match statistics in the /dir/footballstats directory, on top of all container layers. Sharing Data Suppose the FootballStats container has already gathered a certain amount of data, and now it's time to analyze it. For instance, we might want to find out how a particular team performed in the latest national championship or how a specific player did — goals, assists, cards, etc. To do this, we can mount our volume into a new container, which we’ll call FootballStats-Analytics. The key advantage of this setup is that the new container can read the data without interfering with the original FootballStats container’s ongoing data collection. At the same time, analysis of the incoming data can be performed using defined parameters and algorithms. This information can be stored anywhere, either in the existing volume or a new one, if needed. Other Types of Mounts In addition to standard volumes, Docker Volumes also supports other types of mounts designed to solve specialized tasks: Bind Mount Bind mounts are used to attach an existing path on the host to a container. This is useful for including configuration files, datasets, or static assets from websites. To specify directories for mounting into the container, use the --mount option with the syntax <host path>:<container path>. Tmpfs Mount Tmpfs mounts serve the opposite purpose of regular Docker Volumes — they do not persist data after the container is destroyed. This can be useful for developers who perform extensive logging. In such cases, continuously writing temporary data to disk can significantly degrade system performance. The --tmpfs option creates temporary in-memory directories, avoiding constant access to the file system. Drivers Docker Volume Drivers are a powerful tool that enable flexible volume management. They allow you to specify various storage options, the most important being the storage location — which can be local or remote, even outside the physical or virtual infrastructure of the provider. This ensures that data can survive not only the destruction of the container but even the shutdown of the host itself. Conclusion So, we’ve learned how to create and manage storage using Docker Volumes. For more information on how to modify container storage in Docker, refer to the platform’s official documentation. 
09 June 2025 · 6 min to read

Do you have questions,
comments, or concerns?

Our professionals are available to assist you at any moment,
whether you need help or are just unsure of where to start.
Email us
Hostman's Support