Traffic pattern
Tied to office hours, with a scheduled application peak
- Load concentrates in office hours
- Application periods follow a calendar
- Capacity is prepared, not auto-scaled
Solution scenario
A reference architecture for public institutions
In a public sector workload the load usually follows office hours, and the real question is traceability rather than capacity. This page shows how a single controlled entry, nested boundaries and document retention are set up.
- Primary decision
- Where the boundary is drawn and keeping a single entry
- Data layer
- The document archive in object storage, its copy in a vault
- Boundary
- Conformance with legislation is the institution’s assessment
Overview
What is the first architectural question in a public sector workload?
In this scenario the first question is the boundary, not capacity. The system opens outward through a single controlled point; the application front end, the document archive and the backup vault all stay behind it inside two nested boundary frames. Every inbound request passes through the same router and the access record is kept there, because who reached what and when matters as much as the system’s output. The second decision is that the data layer is document-oriented: application attachments and output documents accumulate in object storage, and the retention period is set by institutional policy and the legislation the institution is subject to. The third is the predictability of the load; application periods follow a calendar, so capacity is planned and preparation is preferred over automatic growth. Topics such as KVKK and KEP are requirements of this scenario.
Typical workload profile
Predictable load, accumulating documents
Load concentrates in office hours and application periods follow a calendar, so capacity is prepared in advance rather than auto-scaled. Document volume, by contrast, never falls, because the archive is not deleted. The main tension in the profile lies between predictable traffic and continuously growing retention.
Data volume
Documents accumulate rather than being deleted
- Application attachments in object storage
- Retention set by institutional policy
- Backup copy in a separate vault
Latency and compliance
Traceability comes ahead of latency
- A single controlled entry point
- Access record at the boundary
- KVKK and KEP as scenario requirements
KVKK and KEP are treated as the institution’s architecture requirements. Certificates are issued to vMind Information Technologies.
Reference architecture
Two nested frames, one crossing point
The diagram reads along the spatial axis: an outer institutional network boundary, a managed project boundary inside it and a single path crossing both. The client stands furthest out, the router waits at the boundary, and the application and archive stay innermost. The access record is a side component — not part of the flow but its trace.
PortvMind Cloud services used
Boundary, application, archive and vault
The router owns the boundary and access rules, Compute the application front end, Object Storage the document archive, and Backup the archive’s copy in a separate vault. What distinguishes this combination is that storage is document-oriented rather than transactional; the data is kept to be retained and retrieved, not continuously read.
Router
The single controlled point facing outward and the boundary where access rules are defined.
Compute
The application front end runs on capacity planned around office hours.
Object Storage
Application attachments and output documents accumulate here as an archive.
Backup
The archive’s copy in a separate vault and its retention calendar are set up with this service.
Each service page links back to this scenario; the link is generated from the same list in both directions. All Services
Evaluation criteria
Entry, boundary, retention and legislation
The table covers the entry point, the institutional and project boundaries, archive retention and its copy, and legislative topics. KVKK and KEP enter the architecture as the institution’s requirements. The entry point, boundary layer and archive copy are set at setup.
| Criterion | Question asked | Answer in this scenario |
|---|---|---|
| Number of entries | Through how many points is the system reached? | Through one controlled point; every request passes the same boundary and its record is kept there. |
| Boundary layer | Are the institutional and project boundaries separated? | Yes — two nested frames; the sharing of responsibility is defined by contract. |
| Document retention | Are the archive’s retention period and copy defined? | The period follows the institution’s retention policy, and the copy is kept in a separate vault. |
| Legislative requirement | How do topics such as KVKK and KEP enter the architecture? | KVKK and KEP are treated as the institution’s architecture requirements. |
The certificates are issued to vMind Information Technologies.
Related guides and documentation
Reading on archives, protection and migration
Backup planning, object storage and archive migration are covered in the guides. Setup and API access are in the documentation.
Guides
- What Is Cloud Backup? How to Plan Enterprise Backups
Cloud backup stores scheduled copies of your servers, volumes and application data. With PortvMind Cloud Backup you create, track and restore those copies from the panel. A snapshot is for a fast rollback; lasting protection comes from Backup.
- Object Storage Architecture: How It Differs from Block Storage
Object storage keeps data in buckets as independent objects containing the data, a unique key and metadata rather than filesystem blocks. Applications typically access these objects through an HTTP-based, S3-compatible API. Block storage presents a disk volume to a server, where the operating system runs a filesystem or database. The object model is evaluated for media, backups, archives and data lakes, while the block model suits operating-system disks, databases and workloads that need low-latency random reads and writes.
- S3 Migration Checklist: How to Plan an Object Storage Move
An S3 migration is more than copying files. A controlled move combines source inventory, required API behaviors, metadata and versions, a trial copy, an integrity check, final delta synchronization and a rollback plan. Test the operations your application uses on the target service.
Guides
- Getting Started Guide
Go directly to the account creation guide on Discuss.
- API Access and Application Credentials
A short access overview and the related product announcement on Discuss.
Other solution scenarios
- Manufacturing and Industry
A one-way bridge between the plant and the cloud, and a peak-free continuous stream.
- AI and Data
The training window, checkpoint volume and inference path are planned separately.
- SaaS and Startups
Environment separation, release promotion and a persistent volume per tenant.
Let us write the boundaries and the retention calendar together.
Share your application calendar, archive volume and institutional retention policy; in the architecture consultation we define the entry point, the boundary layers and the backup vault together.