Documentation
Service Types Guide - Choose Your Deployment
Select the perfect service type for your application. Compare web services, private services, and managed databases to deploy with confidence and optimal performance.
deployra Service Architecture
deployra offers a comprehensive suite of service types designed to handle every aspect of modern application deployment. From public-facing web applications to secure internal services and fully managed databases.
Application Services
- Web Services - Public applications with HTTP access
- Private Services - Internal services for secure communication
Managed Databases
- PostgreSQL - Relational database with ACID compliance
- MySQL - Popular relational database for web apps
- Key-Value Store - Redis-compatible in-memory database
Choosing a service type is the first step of creating a new service in the Deployra Dashboard:
Summary of service types
The most common service type. Dynamic web apps with a public deployra.app subdomain for receiving traffic over HTTP.
If you're building a public web app using Express, Django, Rails, or something similar, use this service type.
Dynamic web apps that don't have a public URL. Private services expose an internal hostname for receiving traffic from your other Deployra services over their shared private network.
Private services are great for deploying tools like:
- Elasticsearch
- ClickHouse
For storing data
Fully managed PostgreSQL databases with automatic backups, point-in-time recovery, and horizontal scaling.
Ideal for relational data models and applications requiring ACID compliance.
Managed MySQL databases with strong performance, reliability, and ease of use.
Great for web applications, content management systems, and e-commerce platforms.
High-performance in-memory data store for caching, real-time analytics, and message brokering.
Compatible with Redis clients for seamless integration.
Frequently Asked Questions
How do I choose between web and private services?
Choose web services for applications that need public internet access (websites, APIs, web apps). Choose private services for internal tools, databases, or services that should only be accessible within your deployra network (microservices, internal APIs, monitoring tools).
Can I change service types after deployment?
Service types cannot be changed after creation. If you need to switch from web to private service or vice versa, you'll need to create a new service with the desired type and migrate your application. However, you can always scale resources, change instance types, or modify environment variables.
Which database should I choose for my application?
PostgreSQL is ideal for complex applications requiring ACID compliance, advanced queries, and data integrity. MySQL works great for web applications, content management, and e-commerce. Key-Value stores are perfect for caching, session storage, real-time analytics, and applications requiring high-speed data access.
Can services communicate with each other?
Yes! All services within your organization share a private network. Web services can connect to private services and databases using internal hostnames. This enables secure microservice architectures and database connections without exposing internal services to the public internet.
Are there any limitations on service types?
Web services are limited to HTTP/HTTPS traffic on standard ports. Private services can use any port and protocol within the private network. Database services are fully managed with automatic backups, scaling, and maintenance. All services support environment variables, persistent storage, and horizontal scaling.
How do I connect my application to a database?
Database connection details are provided in your service dashboard, including hostname, port, username, and password. Use these credentials in your application's database configuration. All database connections are encrypted and occur over the private network for maximum security.