High Availability
The Load Balancer continuously monitors its server pool with health checks. Unresponsive servers are automatically removed from traffic and re-added once healthy. Single-server failures are therefore never visible to your users.
Load Balancer (L4/L7)
Keep your service online even when a single server goes down
Regions: tr-ist-01 (İstanbul) · tr-ank-01 (Ankara).
Client traffic enters on the port and protocol the listener defines.
The pool spreads requests over healthy backends with the chosen distribution algorithm.
The health check probes every member on an interval; a member that stops answering leaves the rotation.
Once the member answers again it rejoins the pool on its own; no manual step is needed.
Answer
What is Load Balancer?
Load Balancer is an L4 and L7 service that distributes traffic across servers. A health check removes an unhealthy server from traffic.
Cost depends on load balancer runtime, traffic and attached resources, public ip and additional network components. Review the current estimate in the cost calculator.Calculate Cost
Live capacity and quota depend on the selected resource; service level terms are explained on the SLA page.
Features
Key Features
- Load balancing at L4 (TCP/UDP) and L7 (HTTP/HTTPS)
- Automatic failure isolation with health checks
- Traffic distribution for horizontally scaling applications
- Integrated operation with VKE and Compute services
How it works
How the infrastructure works
AppBalancer or NetBalancer?
The setup flow in the console starts with one of two types. AppBalancer works at the application layer (L7) for HTTP and HTTPS; it understands requests, so distribution by application-level data such as path or header and HTTP health checks are possible. NetBalancer works at the transport layer (L4) for TCP and UDP; it does not inspect content, forwards the connection as-is, and is chosen for non-HTTP traffic such as databases, game servers or custom protocols. Because the choice fixes the layer at which balancing happens, it is not changed later; a new load balancer is created instead.
Listener, Pool and Health Check
A load balancer is defined by three components. The listener sets which port and protocol the balancer accepts traffic on. The pool is the group of backend servers traffic is distributed to, and the distribution algorithm is chosen there. The health check sends a request to every pool member at an interval; a member that stops responding is removed from traffic and re-added once it responds again. Choose the path and expected response of the health check so that it reflects the real state of the backend application; a check that only asks whether the port is open will count an application that is up but failing as healthy.
Public Exposure, TLS and Certificates
The load balancer is created on a private subnet and exposed to the internet through a Floating IP, so backend servers do not need public addresses of their own. For HTTPS, where the certificate is terminated is an architectural choice: terminated at the balancer, backends can speak HTTP; terminated at the backend, the balancer passes the connection through. Certificate and key material is kept in Security > Key Manager in the console. Backend Security Group rules accept traffic only from the balancer's address.
Responsibility Boundary
PortvMind Cloud operates the load balancer, the distribution layer and Floating IP routing. Listener and pool definitions, the health check, the certificate lifecycle and backend capacity belong to your team. Quota appears under Quota. Load-balancer and traffic cost appears in the cost calculator.
Scenarios
Use Cases
- Availability for high-traffic web applications
- Distributing microservice and API traffic
- Zero-downtime (rolling) deployment scenarios
Decision criteria
Responsibility, setup and boundaries
Who manages what?
PortvMind Cloud
- Provide the control plane for creating and managing network resources
Customer team
- Define addressing, routes, ports, access and traffic policy for the workload
What shapes cost?
- Load balancer runtime
- Traffic and attached resources
- Public IP and additional network components
Service boundaries
- Quota and capacity appear in your project settings.
- Regions are limited to İstanbul (tr-ist-01) and Ankara (tr-ank-01).
How do you start in the console?
Hover or press play; the steps light up in time with the recording.
- Choose the load-balancer type
- Select the subnet connection
- Add listener, pool, and health checks
FAQ
Related Questions
How does pricing work?
PortvMind Cloud uses a pay-as-you-go model with per-minute billing. Total cost depends on resource type, selected configuration, storage, network and runtime. Current unit prices are in the console and at calculator.portvmind.com.
Which companies and projects is PortvMind Cloud suitable for?
It suits a wide range from start-ups to mature enterprises: e-commerce and web/mobile applications facing sudden traffic spikes during campaigns, AI/ML and data analytics projects, rapid Prod/Dev/test/QA environments, and microservice-based modern architectures. It is an especially strong option for finance, public sector and healthcare organizations that need sovereign cloud and data sovereignty - Türkiye's cloud.
How do I get started?
Create an account in the console, complete email, phone and card verification, then open your first virtual server in Compute. Use calculator.portvmind.com to plan the cost.
Next step
Test Load Balancer against your own workload.
Create the resource in the console. For a migration or scaling plan, continue together in an architecture consultation.
Model your scenario in the cost calculator.Calculate Cost