LogoLogo
Give FeedbackGovStack Home
Development
Development
  • GovStack
  • Contributing
  • Architecture and Nonfunctional Requirements
    • 2 Introduction
    • 3 GovStack Architecture
    • 4 Building Block Design Principles and Considerations
    • 5 Cross-Cutting Requirements
    • 6 Onboarding Products
    • 7 Standards
    • 8 UI Switching and Handover
    • 9 Other Resources
  • Security Requirements
    • 2 Description
    • 3 Terminology
    • 4 Security Management
    • 5 Cross-Cutting Requirements
    • 6 Standards
    • 7 Authorization Services
    • 8 Additional Security Modules
    • 9 Other Resources
  • Digital Sovereignty - Cloud Infrastructure
    • Abstract
    • Digital sovereign cloud technology
    • Digital Sovereignty considerations
    • Architectural graphics
  • GovStack UI/UX Guidelines
    • 1 Version History
    • 2 Description
    • 3 Service design good practice guidelines
      • 3.1 User-centred design
        • 3.1.1.1 Understand needs and requirements
        • 3.1.1.2 Involve others in the design process
        • 3.1.2.1 Test with users
        • 3.1.3.1 Share findings
        • 3.1.3.2 Monitor performance
          • 3.1.3.3 Set up analytics
      • 3.2 Accessibility and inclusion
        • 3.2.1.1 Test for accessibility
        • 3.2.2.1 Involve a diverse user group in the design
        • 3.2.2.2 Support multiple languages
        • 3.2.2.3 Foster a culture of inclusion
      • 3.3 Consistency
        • 3.3.1.1 Use simple language
        • 3.3.2.1 Implement a consistent style guide
        • 3.3.2.2 Use design patterns
        • 3.3.2.3 Use a frontend framework
        • 3.3.3.1 Interoperability
        • 3.3.3.2 Use integrations
        • 3.3.4.1 Work in the open
      • 3.4 Technology choices
        • 3.4.1.1 Choose the right level of security
        • 3.4.1.2 Design for privacy
        • 3.4.2.1 Optimise load times
        • 3.4.2.2 Account for connectivity issues
        • 3.4.3.1 Test across platforms
        • 3.4.3.2 Design cross-channel
    • 4 Design patterns
      • 4.1 Service patterns
      • 4.2 User flows
        • 4.2.1 Register
        • 4.2.2 Authenticate
        • 4.2.3 Asking users for feedback
        • 4.2.4 Find a service
        • 4.2.5 Check a users eligibility
        • 4.2.6 Make an application
      • 4.3 Page templates
        • 4.3.1 Feedback
        • 4.3.2 Perception survey
        • 4.3.3 Satisfaction
        • 4.3.4 Before you start
        • 4.3.5 Service sheet
        • 4.3.6 Asking users for consent
        • 4.3.7 Task list
        • 4.3.8 Asking users for information
        • 4.3.9 Check answers
        • 4.3.10 Outcome
    • 5 Use-case examples
    • 6 References
    • 7 Other Resources
  • Building Blocks
    • About Building Blocks
    • Consent
    • Digital Registries
    • E-Marketplace
    • E-Signature
    • Geographic Information System (GIS)
    • Identity
    • Information Mediation
    • Messaging
    • Payments
    • Registration
    • Scheduler
    • Workflow
  • Cloud Infrastructure
  • Use Cases
    • Reference Use Cases
  • Public Administration Ecosystem Reference Architecture (PAERA)
    • PAERA
  • Tools
    • Sandbox
  • Release Notes
    • 23Q4
Powered by GitBook

Apache-2.0 license

On this page

Was this helpful?

  1. Digital Sovereignty - Cloud Infrastructure

Digital sovereign cloud technology

Software is only a facet of of the picture “digital sovereignty” (see below), but an important base for it. The decision for a software stack for a governmental environment should be taken consciously and educated. Here are some points to be considered to gain real digital sovereignty:

  • software licenses for all code should be open source allow for free usage and adaption, and offer the capability to contribute to and shape the software

  • the used software should be mature and proven in production, it should be resilient, scaleable, and possible to be used in large and professional environments (like enterprise clouds)

  • the software should be maintained by an active community or foundation to guarantee further development, bug fixes, support, and increased security – the community or foundation should also offer the possibility to contribute, so the national technicians can collaborate on the software development; ideally, the community is diverse and not closely associated with a single entity

  • it should use open, common standards and open interfaces

  • the cloud infrastructure should be automated, integrated, interoperable, and modular federal, so it can be also used in multi or hybrid cloud environments

  • the cloud infrastructure should be independent of the underlying hardware and operation system

  • it should reduce critical dependencies on providers through standardized, modular IT architectures

  • it should allow cross-cloud and reciprocal use of governmental applications, allowing the integration and execution of GovStack building blocks

  • it should cover all security demands and access requirements

  • Additionally: operational knowledge should be available, documented, and further developed by an active community

  • to get scalable, resilient cloud infrastructure it is recommended to have a dedicated IaaS (virtualization) layer with automated rollout and integrated monitoring and security tools

  • for application development and operations, a dedicated scalable self-service container platform is recommended with container orchestration, a container registry, and configuration management

In recent years, open source and open technologies have played an exceptionally important role in the realization of specialized applications in the corporate and government context. However, these also require a technological basis that ensures their sovereignty in the long term. The operating environments or the cloud platforms therefore play an important role here. Of course, these cloud environments can be built from scratch, but there are existing solutions which cover all necessary aspects. Govstack and their partners are happy to help (one example see below).

PreviousAbstractNextDigital Sovereignty considerations

Last updated 1 year ago

Was this helpful?