Our cloud experts have compiled all the important aspects for you and addressed frequently asked questions from our customers to provide you with full insight and complete transparency. Are you only interested in a specific section? No problem, below you can conveniently click on the section that interests you and you will be taken directly there. At the bottom of the page you will also find a whitepaper on Cloud Development with all the information, easy for you to download
.
Content
- What is the reason for this?
- What clouds are there?
- Should I go to a public cloud, a private cloud or a hybrid cloud?
- Which public cloud should I use, AWS, Azure or the Google Cloud? Are there any differences?
- Can I switch cloud providers later?
- Is the public cloud secure?
- What about DSGVO, data protection and compliance in the public cloud?
- Can I migrate any application to the cloud?
- What is Application Modernisation, Application Transformation, “Cloud Native” and “Lift & Shift”?
- Which architecture should I choose? Virtual machines? Platform-as-a-Service? Software-as-a-Service? Container? Kubernetes?
- What does a cloud migration / modernisation cost?
- What steps need to be taken in a cloud migration / application modernisation?
- Will the costs go down if I run my application in the public cloud?
- How do I ensure the availability and operation of my application in the public cloud?
- What options does the public cloud offer me in terms of scalability of my application?
- How do I train my team so that I can later develop my application in the cloud myself?
Why should I move an application to the cloud?
Summary
Application development in the cloud is one of the most important growth areas in the IT world due to the advantages that the cloud offers: fast development speed, easier maintenance, scalability, higher reliability, flexible cost model and higher security. However, there are also aspects that need to be considered in order to develop successfully in the cloud.
What is the reason for this?
The development and operation of applications in the cloud, i.e. the use of cloud development, is one of the main growth areas in the entire IT world.
Development speed
Clouds offer special services that extremely accelerate software development (“Platform-as-a-Service” or “Cloud Native”). Databases and storage space, for example, can be used directly for the application. This drastically reduces the time it takes for an application to “go-live” in development.
Maintenance
In the cloud, many aspects are taken off the company's hands. Backups become much simpler, and with intelligent design, there's no need to update operating systems, etc. The focus can then shift to the development and operation of the application itself, as the "surroundings" are managed by the cloud and the benefits of cloud development.
Scalability
With intelligent design of the application, the computational power can be scaled from 0 (no cost) to almost infinity (millions of concurrent users all able to use the application fluidly at the same time).
Reliability
The cloud providers ensure high availability and corresponding redundancy, even in the event of a fault. A large part of the entire Internet is based on the cloud – a failure would have correspondingly fatal consequences. That’s why high availability is inevitably a key element in the cloud as well as cloud development itself.
Costs
The model mentioned under "Scalability" can be directly applied to costs as well: When the application is not being used (for example, during the night), it scales down to zero, resulting in no costs. At noon, when millions of users are using the application simultaneously, the infrastructure scales up accordingly, and you pay for the resources you're utilizing.
Security
Clouds offer higher security compared to classic hosting in a data center. Security is the central element in all clouds and is ensured on the front line by the respective hyperscalers – with huge teams of experts specializing in exactly this, in a way that a data center could not provide. In addition, backups and recovery are included directly, which is often a bigger issue with classic hosting.
What clouds are there?
Summary
When it comes to Cloud Development, there are three types of clouds: Private Clouds, Public Clouds, and Hybrid Clouds. Private Clouds are reserved for a specific organisation and offer limited scalability and features, while Public Clouds are operated by hyperscalers like Amazon, Microsoft, and Google, providing unlimited scalability, high speed, security, and flexibility. Hybrid Clouds combine the benefits of both cloud types to achieve maximum control and speed.
Cloud types
A basic distinction is made between 3 different types of clouds: private clouds, public clouds and hybrid clouds. All 3 variants have different focuses.
Private Clouds
A cloud that is provided only to a specific organisation and is not available to the public. Compared to the public cloud, the range of functions is more limited, but offers greater flexibility and faster provision of computing power/infrastructure.
Public Clouds
Cloud providers such as Amazon AWS, Microsoft Azure and Google GCP, which offer arbitrary scalability and provide the best overall package for most use cases in terms of speed, cost, scalability and security.
Hybrid Clouds
A combination of Private Cloud and Public Cloud that operates selected applications in the Private Cloud, and then the majority in the Public Cloud, aiming to merge the advantages of both worlds. The contents are integrated to facilitate seamless interaction.
Should I go to a public cloud, a private cloud or a hybrid cloud?
Summary
The choice between Private, Public, or Hybrid Cloud depends on the specific Cloud Development use case. Often, a combination of Private and Public Cloud proves to be the optimal solution, with new business models and modern applications/services developed in the Public Cloud, and existing applications and workloads migrated to it. Ensuring seamless harmony between the Private and Public Cloud is crucial.
Use case dependency
You have probably already guessed what we're going to say here: A blanket answer to this question is not possible because it depends on the specific application. But one thing can be said in general terms: Relying exclusively on a private cloud leaves a lot of untapped potential. Relying exclusively on the public cloud can make sense if the structures within the organisation are in place for this:
- Is there openness and willingness within the company?
- Do the technical skills and understanding exist?
- Is there support from management?
A combination of private cloud and public cloud is often the most realistic scenario – the hybrid cloud. New business models and modern applications/services are developed directly in the public cloud. Existing applications and workloads that are a good fit are migrated to the public cloud to take full advantage. Legacy applications and particularly sensitive data and applications remain in the private cloud and are migrated either successively or not at all – depending on the company’s governance/policy.
It is important that the private and public cloud realms correspond and harmonize with each other.
Which public cloud should I use, AWS, Azure or the Google Cloud? Are there any differences?
Summary
The three main hyperscalers all offer similar benefits, such as rapid and secure application development and scalability. The choice of hyperscalers depends on what services and applications are already in place in the enterprise and what the scalability, security and pricing requirements are. Weighing the pros and cons and a decision matrix with the service provider’s recommendations can help with the choice.
The differences
There are some differences between the 3 most relevant hyperscalers – again, it all depends on what (a) is already there and (b) is left to be done. Basically, it can be said that applications can be developed and operated quickly, securely, flexibly, cost-effectively and scalably on all 3 hyperscalers. All 3 hyperscalers have numerous data centres, both in Germany, Europe and around the world. All 3 hyperscalers offer virtually unlimited compute power and scalability. All 3 hyperscalers offer numerous services for rapid software development.
Often the question of choice does not even arise because a cloud has already been established in the company and framework agreements exist. In this case, the issue has already been resolved and the next steps are:
- "What needs to be done?" and
- "How should it be specifically implemented?"
This usually involves collaborative discussions between business owners and architects within the company and experts from the service provider. The goal is to align the company's technical requirements with the planned architecture of the application.:
- Are there certain specifications as to which services may / should be used in the public cloud?
- What are the scalability and high availability / redundancy requirements?
- Are there requirements for encryption in data storage and data transmission?
- …
Can I Switch Cloud Providers Later?
Summary
By adhering to certain design principles, portability between different cloud providers can be enabled. Tools such as Terraform and Infrastructure as Code enable automated setup of environments and applications. However, completely automated switching between cloud providers rarely makes sense and involves higher costs. It is advisable to clarify together with the service provider which degree of portability is desired and to take this into account already in the design of the application.
Cloud change – the conditions
In principle, you can switch to a different cloud provider at a later date, but certain principles in the design of the application must be taken into account for this. Tools like Terraform (Infrastructure as Code, IaC) can automate the complete setup and provisioning of the environment and the application itself—without a single click. Such approaches make it considerably easier to make a potential switch later on. However, it should also be fairly stated: A 100% automated switch from one cloud to another is possible, but rarely makes sense and is associated with higher costs in design and implementation.
Therefore, we recommend discussing the desired level of portability with the service provider before implementation and taking this into account in the application's design.
Is the public cloud secure?
Summary
Security in the public cloud and cloud development is important and depends on several factors. Public cloud providers invest in the security of their infrastructure and services, but the security of applications and data also depends on the user’s own security measures.
The question of security
Key aspects of public cloud security include infrastructure security, data encryption, identity and access management, monitoring, compliance, and certifications. Cloud security is a shared responsibility between the provider and the user, with the user being responsible for application and data security. Best practices should be applied to proactively protect security.
Some important aspects at a glance:
Infrastructure security
Public cloud providers invest in protecting their data centres and networks to ensure high security for their customers. These include physical security measures, access controls, network security and security monitoring.
Data encryption
To ensure data protection in the public cloud, providers offer encryption for both data at rest (stored data) and data in transit (transferred data). Users can and should consider additional encryption measures for particularly sensitive data.
Identity and access management
Public cloud providers provide services that allow users to manage their authentication and authorisation policies. This enables control over who can access which resources and services in the cloud.
Safety monitoring and logging
To detect and respond to potential security incidents, cloud providers offer monitoring and logging services that allow users to continuously monitor your cloud resources and identify potential threats.
Compliance and certifications
Public cloud providers have certifications and security audits to prove compliance with standards. Companies should consider the compliance requirements of your industry and ensure that the chosen provider meets them. Security in the public cloud is a shared responsibility between provider and user. Companies should adopt best practices, establish a specific security plan with their service provider, and proactively protect their data.
What about DSGVO, data protection and compliance in the public cloud?
Summary
In the public cloud and cloud development, GDPR is important. Providers such as AWS, GCP and Azure meet the requirements. Companies should pay attention to GDPR compliance and implement security measures. A data protection impact assessment may be necessary to identify risks.
On the safe side
GDPR is important for companies in the EU and those doing business with EU citizens. In the public cloud, GDPR, data protection and compliance are critical to meeting regulatory requirements.
DSGVO compliant cloud providers
Most major public cloud providers have adapted their services to GDPR and offer tools to provide GDPR-compliant services. It is important to choose a GDPR-compliant cloud provider and sign a data processing agreement.
Data processing agreements
Companies should ensure that they enter into appropriate Data Processing Agreements (DPAs) with their cloud providers that govern the processing of personal data in accordance with the GDPR rules.
Data storage and transmission
DSGVO and data protection in the public cloud require secure storage and transfer of personal data. Companies should know where their data is processed and that the transfer is secure. Regional data storage options can help ensure compliance with privacy laws.
Security measures
Companies must implement appropriate security measures to protect personal data in the cloud. This includes encryption, access controls, monitoring and regular security audits. Public cloud providers have implemented comprehensive security measures.
Data protection impact assessment
In some cases, a data protection impact assessment is necessary to identify risks when processing personal data in the public cloud. Companies ultimately bear the responsibility for adherence to GDPR and compliance in the cloud. A GDPR-compliant cloud provider and appropriate security measures and data protection policies are important steps to meet compliance requirements and gain the trust of customers and partners.
Hyperscaler
The three hyperscalers AWS (Amazon Web Services), GCP (Google Cloud Platform) and Azure (Microsoft Azure) are leading providers of public cloud services and attach great importance to data protection, DSGVO and compliance.
Can I migrate any application to the cloud?
Summary
The suitability of an application for cloud migration depends on various factors, such as the current architecture, the technologies used and the specific requirements of the application. Some application types that are well suited for cloud migration include scalable, stateless applications and applications on microservices architectures.
However, it is possible in principle to migrate a wide range of applications to the cloud. A careful analysis of the application and its requirements is necessary to evaluate the suitability of an application for cloud migration.
The suitability of the application
In principle, it is possible to migrate a wide range of applications to the cloud. However, the suitability of an application for cloud migration depends on various factors, such as the current architecture, the technologies used and the specific requirements of the application.
Some application types that are well suited for cloud migration include:
- Scalable applications: Applications that are designed so that you can scale horizontally or vertically to respond to changes in load or demand particularly benefit from cloud infrastructure.
- Stateless applications: Applications that do not store internal state and whose components operate independently of each other are well suited for the cloud because they can be easily distributed across different resources.
- Microservices architectures: Applications based on a microservices architecture tend to migrate well to the cloud because you can take advantage of the scalability and flexibility that cloud platforms offer.
However, there are also application where cloud migration can be more difficult or less useful:
- Legacy applications: Older applications based on outdated technologies or architectures may have difficulty migrating to the cloud. In some cases, it may be necessary to modernize or redevelop the application to make you ready for the cloud.
- Applications with strict compliance or data protection requirements: Some applications are subject to strict regulatory or data protection requirements that may limit the scope of cloud migration. In such cases, customers must carefully check whether the selected cloud platform meets the required standards.
- Latency-sensitive application: Applications that rely on real-time processing or ultra-low latency can be impacted by a cloud migration if the latency between the cloud and end users or other systems is too high.
Deciding whether an application is suitable for cloud migration requires a careful analysis of the application and its requirements, and a consideration of the potential benefits and challenges that cloud migration can bring.
What is Application Modernisation, Application Transformation, “Cloud Native” and “Lift & Shift”?
Summary
There are a few terms that are important on the path to cloud migration. Application Modernisation means the updating of applications, while Application Transformation means a fundamental adaptation to new requirements. Cloud Native is an approach to developing applications specifically for the cloud environment. Lift & Shift is a strategy for migrating applications to the cloud without making changes to the application itself.
Terminology
On the way to the cloud, you encounter many terms that can be quite confusing at first. Some of the terms we encounter most often when guiding our customers’ Cloud Journey are as follows:
Application Modernisation
App modernisation improves existing applications to keep pace with latest technologies and requirements. The upgrade may include architecture, platform, database, user interface and functionality. The aim of the migration is to transfer to a more modern platform with retained functions and business processes. Benefits include improved usability, higher performance, security and scalability.
Application Transformation
App transformation refers to the fundamental change of applications to adapt them to new business requirements. This can include revising business processes, integrating new technologies, migrating data, and customizing the user interface. The goal is to align the application with the business needs and vision of the organisation to improve efficiency, performance and agility.
Cloud Native
Cloud Native applications are built specifically for cloud environments and take advantage of the cloud to perform and scale better. The architecture consists of microservices packaged in containers that use automated processes to deploy, scale and manage applications. The benefits are greater scalability, agility and flexibility, and faster time to market.
Lift & Shift
Lift & Shift is a strategy for migrating applications to the cloud without making changes to the application itself. The goal is to take advantage of the cloud without reengineering the application. One example is the migration of virtual machines or databases to the cloud. However, an application that is not optimized for the cloud can lead to higher costs and poorer performance.
Which architecture should I choose? Virtual Machines(VMs)? Platform-as-a-Service(PaaS)? Software-as-a-Service(SaaS)? Container? Kubernetes?
Summary
The choice of cloud architecture depends on the specific requirements and goals. The main options are: virtual machines(VMs), platform-as-a-service(PaaS), software-as-a-service(SaaS), containers and Kubernetes. Enterprises can combine these options to best meet their cloud development needs.
Architecture choice
The choice of architecture depends on your specific requirements and goals. Here you get an overview of the most important options:
Virtual Machines (VMs)
If you need full control over operating systems and applications, VMs are a good choice. With VMs, you can run a variety of operating systems and applications running on the same physical host.
Platform-as-a-Service (PaaS)
If you want to focus on application development instead of worrying about infrastructure, consider PaaS. PaaS provides a fully managed platform for application development, including scaling and maintenance.
Software as a Service (SaaS)
If you need a fully managed application and don’t need complete control over infrastructure, consider SaaS. SaaS applications are hosted and managed by vendors, so you only pay for what you use.
Containers
If you want to simplify application deployment, containers are a good choice. Containers provide lightweight virtualisation where applications and their dependencies can run in isolated containers.
Kubernetes
If you need container orchestration, consider Kubernetes. Kubernetes provides a platform for automating container deployment, scaling and management. All cloud providers offer a managed Kubernetes environment, so running containers in Kubernetes requires less effort.
It should be noted that these options are not necessarily mutually exclusive and can be combined individually. In many cases, companies use a combination of technologies and architectures to best meet their needs.
What does a cloud migration / modernisation cost?
Summary
The cost of a cloud migration or modernisation depends on a number of factors, including planning and consulting, implementation and migration, training and education, ongoing costs, and maintenance and support. It is important to perform a detailed cost analysis before beginning the cloud development project to gain a better understanding of the expected total cost and potential cost savings.
The cost of a cloud migration or modernisation varies widely depending on the scope and complexity of the project, the resources available and the specific requirements of the application. In general, the total expense is made up of various factors:
Planning and consulting
The planning phase, including assessing current infrastructure, creating a migration plan and selecting the right cloud platform, can vary depending on the complexity and size of the project. The cost of external consulting services can also account for a significant portion.
Implementation and migration
The actual migration or modernisation of the application requires time and resources to adapt the application to the cloud environment, migrate data and systems, and test the application in the new environment. Depending on the scope of the project and the complexity of the application, the cost of this step can vary greatly. Detailed information on migration and modernisation can be found in the following section “What steps need to be taken for a cloud migration / application modernisation?”.
Training and education
Adoption of cloud technologies often requires training and education for the internal team to ensure you have the skills to manage and, if necessary, evolve the application in the cloud. The cost of training and workshops depends on the number of employees involved and the depth of knowledge required.
Current costs
After migration or modernisation, there are ongoing costs for using the cloud infrastructure, such as storage, computing power, bandwidth and services used. These costs vary depending on the provider, consumption and selected billing model. It is important to understand and regularly review the cost structure of your chosen cloud provider to identify potential cost savings. Here, the Public Cloud Group can support you with specific offers for cost management on all hyperscalers.
Maintenance and support
Maintenance and support costs can also vary depending on whether maintenance is internal or external and what service level agreements (SLAs) are in place.
Since the cost of a cloud migration or modernisation depends on many factors, it is important to perform a detailed cost analysis before starting the project to get a better understanding of the expected total cost and potential cost savings.
What steps need to be taken in a cloud migration / application modernisation?
Summary
The steps for a successful cloud migration are customized. Basic milestones include assessing the existing application and IT infrastructure, selecting the appropriate cloud platform, developing a migration and modernisation plan, migrating or modernizing the application, optimisation and monitoring, and training the team. A training program is important to ensure that the team has the necessary knowledge.
Step by step
The steps for a successful cloud migration or application modernisation in cloud development can vary depending on the company and requirements and are individually coordinated depending on the needs.
Basic milestones on the Cloud Journey that have stood the test of time are as follows:
Assessment of the existing application
An assessment of the existing application and IT infrastructure is the first step for a successful cloud migration or application modernisation. For example, the architecture is evaluated in terms of scalability and security, and non-functional requirements are considered.
Choosing the right cloud platform
The appropriate cloud platform should be chosen to meet the requirements of the application. Various factors such as existing programming languages and databases, scalability and security, internal company infrastructure and experience level of the development or operations team play a role.
Development of a migration and modernisation plan
A migration plan should be created that defines steps, expected costs, resource requirements, timeline and risks of migrating or modernising the application to the cloud.
Migration and modernisation of the application
Once all requirements are met, the actual migration can begin. Depending on the requirements and the agreed process model, this is done step by step or holistically.
Optimisation and monitoring
After migration or modernisation, the application should be automatically monitored and optimized to ensure that it works optimally. Monitoring is designed to detect problems early to proactively prevent malfunctions. Optimisation offers opportunities for cost reduction, e. g., through rightsizing or fine-tuning cloud-native services.
Training and training programs
Targeted training program for the application team is important to ensure that the team has the necessary knowledge. A handover workshop can help cover important topics, while other workshops can provide an introduction to cloud-native development. The Public Cloud Group offers corresponding workshops here.
Will the costs go down if I run my application in the public cloud?
Summary
If you're considering whether to use Public Cloud, hardware costs shouldn't be the main factor in your decision. There are other benefits like reduced management effort, secure systems, and flexibility/agility. Public Cloud and cloud development allow for quick responses to market changes and application requirements. With proper optimisation, however, operating costs in the cloud can even be cheaper than in your own data centre.
Cost reduction & advantages
If we reduce the pure cost of running an application to the cost of hardware, then by all means. However, this approach falls short and should not be the main factor in deciding for or against the use of the public cloud. There are some benefits beyond just looking at hardware costs. These include:
Reduced management effort
By reducing the effort required to manage infrastructure, employees can focus more on generating added value for customers and thus on the core of their activities.
Secure systems
Almost every day there are new patches and updates for firmware and software used to host applications. If these are not kept up to date, security gaps arise that can make a system insecure and thus a security risk for the company, their (customer) data and thus also the company’s reputation. Avoiding this requires a lot of time and good management, which is handled by the hyperscaler when using the public cloud. The result is always secure and up-to-date systems.
Flexibility and agility
Having built an application once and then running it forever is no longer enough today. The market is changing rapidly and the requirements for applications are also continuously evolving. For example, scaling applications depending on the number of users of the application. This is precisely the aspect for which the use of a public cloud is excellent. The large number of services and tools that can be used and scaled as needed within a very short period of time allows a company to react and use the full potential.
There are significantly more reasons to opt for a public cloud and cloud development than the pure cost consideration, but with proper optimisation of the systems, they can additionally be cheaper than running the applications in your own data centre.
Lift & Shift vs. cost
A pure lift & shift (“all VMs to the cloud”) often results in higher costs, so modernising the applications and adapting them to the advantages of the cloud is a frequently chosen, sensible and cost-saving path.
How can I ensure the availability and operation of my application in the public cloud?
Summary
To ensure high availability and operational security of applications in the public cloud, some best practices should be followed. These include scalability, resilience, monitoring and logging, security and automation. Automation reduces errors and speeds recovery in the event of failures.
Ensure availability
Ensuring the availability and operation of applications in the public cloud requires some specific measures to ensure that they always run smoothly and are highly available. Here are some best practices to keep in mind when deploying to the public cloud:
Scalability
One of the main advantages of the public cloud and cloud development is its ability to scale. Scaling applications can ensure that they meet the increasing demands of growing user numbers. Automated scaling capabilities and automatic load balancing are easy to set up and manage in the public cloud but depend on the architecture of the application and the infrastructure chosen.
Fail-safe
The public cloud offers several options for resiliency, such as multi-zone deployments and multi-region deployments. Distributing applications across multiple zones or regions can ensure that it is still available if one area fails.
Monitoring and logging
Continuous monitoring of the application is essential to minimise potential downtime. A central monitoring system makes it possible to detect faults, performance problems and other potential malfunctions.
Security
To ensure high availability and operational reliability, security aspects such as data protection, network security, authentication and authorisation must also be taken into account.
Automation
Automation of processes such as provisioning, scaling, and recovery of resources and applications reduces the likelihood of failures and speeds recovery should outages occur despite all measures.
What opportunities does the public cloud offer me in terms of scalability of my applications?
Summary
Cloud development offers many ways to scale applications, including horizontal and vertical scaling, load balancing, container orchestration and serverless computing. Horizontal scaling involves adding new instances, while vertical scaling increases resources such as CPU and memory. Load balancers distribute traffic across multiple instances, container orchestration systems simplify application scaling and management, and serverless computing runs code without server management. The choice of the best scaling strategy depends on the specific requirements and architecture of the application.
Scaling
The public cloud offers numerous options for increasing the scalability of applications and dynamically adapting resource consumption to requirements.
Some of the key scaling options in the public cloud include:
Horizontal scaling (Auto Scaling)
Horizontal scaling involves adding new instances of an application or infrastructure components to spread the load and increase performance. Cloud providers typically offer auto-scaling tools that automatically start or shut down new instances based on predefined rules and metrics, such as CPU utilisation or number of requests.
Vertical scaling
Vertical scaling increases or decreases resources, such as CPU, memory, or I/O, for existing instances to improve performance and efficiency. This is especially useful for applications that are not easily scalable horizontally. In the public cloud, vertical scaling is often easy to do by adjusting the size of the instances.
Load Balancer
Load balancers distribute traffic across multiple instances of an application or infrastructure components to ensure even load distribution and avoid bottlenecks. Elastic load balancers are available in the public cloud that scale dynamically to adapt to traffic and the number of instances backed up.
Container Orchestration
Containers provide lightweight virtualisation and allow applications and their dependencies to run in isolated environments. Container orchestration systems like Kubernetes can simplify the scaling and management of applications in the public cloud by automatically adding or removing containers to balance load and increase availability.
Serverless Computing
Serverless computing, such as AWS Lambda, Google Cloud Functions, or Azure Functions, allows code to run without managing servers. These services scale automatically to meet application requirements and are typically billable on an event or request basis.
The public cloud offers a wide range of scaling options that make it possible to optimise application performance and availability while keeping costs under control. The choice of the best scaling strategy depends on the specific requirements and architecture of the application.
How do I train my team so that I can later develop my application in the cloud myself?
Summary
There are various ways to acquire knowledge about Cloud and Cloud Development. One way is the theoretical approach, where major cloud providers offer structured learning content and certifications. The consulting approach provides lectures and training sessions conducted by consultants to deepen specific topics. A practical approach involves using sandboxes provided by large cloud providers to test their services. The collaborative "team" approach, where developers and consultants work together on project implementation, offers a combination of theoretical and practical methods and allows for continuous knowledge exchange.
Training opportunities
There are several ways to build up knowledge in order to be able to develop applications in the cloud yourself:
Theoretical approach
Each hyperscaler offers different “learning paths”. These are structured learning contents compiled for specific target groups. They cover all the basic information needed to get started with cloud and also cloud development. To check whether the knowledge is available, certificates can be obtained. However, the purely theoretical approach usually falls short, as challenges arise in practice that cannot all be covered by training material.
Consulting approach
Consultants are another way to gain knowledge on specific topics. Knowledge is imparted through lectures and training sessions, which can then be deepened with practical exercises and the support of the consultant. For the most part, however, this approach only covers a few topics in depth, which falls short in some cases for further development of the application.
Practical approach
For teams that like to learn by doing, major cloud providers offer sandbox environments where you can freely test out their services. Usually, you get a set amount of credits to use these services for a limited time. While this hands-on approach is great for gaining practical experience, the sheer variety of services can sometimes be overwhelming.
Team-based approach
In our opinion, the best approach is to combine theoretical foundations with practical application by implementing a real project. We often work collaboratively with clients on the implementation of their applications. This approach, which we refer to as "Team Leasing," ensures continuous knowledge exchange.
This two-way partnership is a win-win. It allows us to quickly grasp the unique aspects of the client's business, while the client gains the advantage of our cloud development know-how, picking up essential skills for future projects as we go along.
This approach can be adapted depending on the project and team size. For example, we can integrate developers from our client's team into our existing teams, which may also include Product Owners. This allows us to cover not just technical topics but also aspects of agile project management.