Review of our Google Cloud Zürich Meetup #6

The Google Cloud Meetup #6 took place on November 10, 2020 in Zürich City in the cafeteria of nine. Due to local restrictions, we were not allowed to have guests in the cafeteria, therefore all participants were online on YouTube. Thanks to Google who would have sponsored pizza and beer!

Thomas Hug, Founder of nine introduces the speakers Matthias Isler, CTO of GetYourLawyer AG and Jonas Felix, Founder of Letsboot.com.

Migrating a Marketplace to Google Cloud – From VMs and Bash Scripts to GKE and CI/CD Pipeline

GetYourLawyer is the leading platform for legal services in Switzerland. Founded in 2017 with the goal of automating documents for law firms, the start-up has developed continuously and brought in 2019 Ringier Axel Springer on board as an anchor investor. The GetYourLawyer platform is technically based on the Laravel Framework (PHP) and Node.js. There are connections to various other systems such as SAP. The frontend of the application is based on Vue.js. The decision to migrate to the cloud was based in particular on the scalability now available and the increased availability and security. The expandability and extended control over the infrastructure by GetYourLawyer were also decisive criteria. Thanks to the new infrastructure, the application now implements the “Twelve-Factor App Principles” and large parts of the DevOps approach. Since all data must be stored in Switzerland, the decision was made to use Google Cloud instead of AWS or other providers. The very advanced container orchestration Kubernetes Engine offered by Google also supported this decision. Before the migration, GetYourLawyer’s entire platform was run on a virtual machine, the deployment process consisted of bash scripts that were executed on the VM. The environment was locally recreated with Vagrant.

The new infrastructure consists of an Ingress Load Balancer, three deployments for different tasks and various managed services from Google, e.g. Cloud SQL or Cloud Memorystore. Additional services are provided by nine, including the complete monitoring and supervision of the infrastructure as well as a solution for administration and evaluation of logs.

Based on Bitbucket, a fully automated CI/CD pipeline was built, which enables the delivery of new versions within minutes. The releases are automatically tested in the background to ensure their functionality.

By implementing the Infrastructure as Code (IaC) approach, the complete infrastructure can now be managed and developed by GetYourLawyer’s development team. Previously, the infrastructure was a black box that could only be changed by system administrators.

Now the application is executed on containers (dockers) instead of virtual machines, so the local development environment is no longer necessary. The developers can now start and use the cloud environment locally. In order to make the application executable on a cloud environment, various extensions were necessary, but the effort was kept within limits thanks to the use of a modern framework.

Thanks to careful preparation and comprehensive testing, the actual migration was completed in 28 minutes instead of the 8 hours announced for safety reasons.

In the end, valuable experience was gained from the project, which lasted a total of 9 months. GetYourLawyer’s development team now has comprehensive knowledge about the secure operation of applications on cloud environments and especially Kubernetes.

Not least thanks to the professional support of nine, the migration from GetYourLawyer to the cloud can be considered a complete success.

Challenges in Hands-On training Software Developers on Kubernetes CI/CD

Text by Jonas Felix, Letsboot.com.

It’s challenging to build an intensive and efficient hands-on course for software developers to learn containerization with Kubernetes and CI/CD (because if you can’t automate it, you’re doing it wrong). Everything is code and our trainings are no exceptions. Doing code focussed training for several years, we built several courses with chapters consisting of slides (with reveal-md as code), exercises and an incremental course project having a solution-patch for each chapter. This way participants can work through the material efficiently and vary how much they want to challenge themselves as well as quickly catch up if there is any issue. This leads to very intense training, with a nice rhythm between explanation, exercises and support through the trainers.

Having visited several Container (Docker) and Kubernetes, as well as cloud related courses, we were longing for the same hands on course experience with a big variety of examples for this area. Especially with CI/CD, as automation has to be the absolute core of your container world. We don’t want to teach containers or Kubernetes without automation. To get this kind of experience with containers you need the local container tools, a local cluster, a git project (per participant), a ci / cd pipeline, private container registry, “production/stage” cluster for delivery and a diverse example application / scenario.

Doing this on the participants machines is very hard as you have many moving parts (not just code), different tools and versions. Participants don’t want to use their credit cards. Setting up separate authentication for each participant often leads to initial issues during the setup phase, which is not an effective use of time. Overall the “not on my machine” debugging block training.

To solve this we automated the whole training setup providing a developer instance for each participant on Google Cloud Platform. In addition everyone gets a personal git fork of the course project, a complete GKE production cluster, a local cluster, a private registry, a gitlab-ci pipeline as well as all the authentication set up automatically. Thanks to this automation, we can spin up 10 environments for 2-3 days of training, having 48 servers running to provide separate playgrounds and super realistic environments for each participant.

Thanks to the GCP pricing structure as well as API and the Gitlab API the cost is comparably low per participant and everyone can finally play through all the steps to containerize a diverse application, configure how it should be run on Kubernetes, deploy it on a local developer cluster, run it on a production cluster as well as build a CI/CD pipeline automating everything.

Tools we use for the setup and training:

Further outlook

Our next Google Cloud Meetup is planned for January 12, 2021 16:00 in Zürich City at Stauffacher (nine offices, Badenerstrasse 47). Join us on-site with pizza & beer by Google or remote on Youtube!

If you have an interesting project running on Google Cloud that you want to show or if you have anything else to talk about, please contact us! We also very much appreciate suggestions for topics and possible speakers, by either meet-up-message, by using the contact form on our website, or via email to one of your contacts here at nine. We would like to keep things exciting. We look forward to seeing you again!

Check out our Meetup Group on meetup.com for upcoming Google Cloud Meetups:

Google Cloud Meetup

We plan regular events (either at our offices or in an external location) with interesting speakers and a possibility to network. Everyone that works with or is interested in …

Check out this Meetup Group →

Review of our Google Cloud Zürich Meetup #5

The Google Cloud Meetup #5 took place on 25 August 2020 in Zürich City in the cafeteria of nine. Since the beginning of the year, we have been recording all our Meetups and publishing them on our YouTube Channel. Corona made it necessary to adapt Meetups and hold them online. Starting with this Meetup, we are combining the online experience (via Google Meet) together with the benefits of on-site events such as networking and having pizza and beer together! Thanks to Google for sponsoring pizza and beer!

Thomas Hug, Founder of nine introduces the speakers Thilo Rossa of Parashift and Cyrill Troxler of Nine Internet Solutions AG.

Addressing the challenges in Document Capture with a Cloud-first and Machine Learning approach 

Contrary to popular belief, document processing is anything but solved. And the need for it to be solved is growing as companies are desperate to find ways to reduce costs, increase productivity, process continuity and system efficiency.

In his talk, Thilo Rossa gave insights into the existing challenges in Document Capture and Parashift’s solution approach to address these. Two major aspects of the strategy to actually bring more autonomy into the process at scale are the fundamentally global and highly scalable Google Cloud infrastructure as well as a versatile machine learning platform, capable of coping with the complexity of real-world documents.

The underlying model training architecture consists of five parts. Namely, a backend based on the Google Cloud Platform and Google Cloud SQL, the persistent Google Cloud Storage and AI Platform, the Google Container Registry and DaemonSets along with prediction pods. Both the backend as well as prediction engine are two Kubernetes clusters, each consisting of various nodes and therefore offering great flexibility in terms of organizing, deploying and auto-scaling container applications.

Crossing the Kubernetes Control Plane

Wouldn’t it be great if developers could use the same tools for deploying applications and provisioning supporting infrastructure like databases? In Cyrill Troxler’s talk, he explains this problem and looks at some existing solutions that could improve the situation.

A lot of companies on Google Cloud use tools like Terraform to provision this kind of infrastructure. But all of these tools introduce new workflows that are cumbersome to integrate into existing development workflows. Luckily, if you are using Kubernetes to deploy your applications there are a number of new tools that tackle this problem. We take a look at two of these tools: Config Connector, which is a service from Google that can be enabled as an addon for GKE and Crossplane, which is an Open Source project that recently got accepted into the CNCF sandbox. The talk goes a bit deeper in what makes Crossplane stand out from other tools and shows a live demo of provisioning some infrastructure with it using the Kubernetes control plane.

Further outlook with the new online experience

Our next Google Cloud Meetup is planned for November 10, 2020 17:45 in Zürich City at Stauffacher (nine offices, Badenerstrasse 47). Join us on-site with pizza & beer by Google or remote through Google Meet in your browser!

If you have an interesting project running on Google Cloud that you want to show or if you have anything else to talk about, please contact us! We also very much appreciate suggestions for topics and possible speakers, by either meet-up-message, by using the contact form on our website, or via email to one of your contacts here at nine. We would like to keep things exciting. We look forward to seeing you again!

What is the Public Cloud and what are typical use cases?

Cloud computing has been established for a long time. The advantages over the classic supply of IT services in the own data center are becoming increasingly dominant. The question for companies is therefore not whether they should use cloud computing, but what type of cloud model or which provider they choose.

The public cloud is very attractive for companies because of its direct availability. A public cloud is an IT service delivered by a provider via the public Internet. Users do not need to install or operate their own hardware. They share the public cloud provider’s infrastructure with other companies. However, data and applications are usually completely separated from each other.

The so-called Hybrid Cloud and Multi Cloud are also in high demand. With the Hybrid Cloud, the advantages of public and private clouds can be combined in a common cloud environment. The Multi Cloud creates a cloud environment consisting of several public clouds.

In the following article, we would like to give you an understanding of the Public Cloud. We explain what a public cloud is, what advantages it offers, and where its limits are. Furthermore, we will dispel any misconceptions: A public cloud is less secure than a private cloud. A few use cases are intended to illustrate the sensible use of the public cloud.

The Public Cloud in Detail

Regardless of whether private or public cloud, cloud computing distinguishes between these three basic service models:

  • Software as a Service (SaaS)
  • Platform as a Service (PaaS)
  • Infrastructure as a Service (IaaS)

Source: Google Cloud Blog 

While IaaS provides customers with virtualized IT infrastructure such as computing power, networks, or storage space, PaaS provides runtime and programming environments for developing or operating their own applications. An example of an IaaS service is the nine cloud servers. They provide customers with computing power, storage space, and network connectivity. With the Managed Google Kubernetes Engine (GKE) from nine, you get an offering that can be ranked under PaaS. SaaS makes applications or software available over the Internet. Typical examples are Google Docs, Sheets, Slides, and Forms for the collaborative creation of text documents, tables, presentations, and questionnaires. 

The services of a public cloud are available to customers via the public Internet. Companies select the services they need themselves and order them from their cloud provider. It is not necessary to install and operate their own IT infrastructure for these services. The provider operates and manages the hardware and software (depending on the service model) in its data centers. For example, employees of the provider maintain servers, operating systems, and software, apply updates and patches, monitor the performance of the computers, secure the systems against hackers or unauthorized access and ensure high availability through redundancy. If a customer needs more performance, he can flexibly expand the services via web-based self-service user interfaces. The services are easily scalable and adapt to the needs of the company. The services used are generally billed on a usage basis. Customers of a public cloud only pay for the services and resources they have actually ordered and used.

Difference between Public Cloud and Private Cloud

In contrast to a public cloud, the services of a private cloud are not available to the general public, but only exclusively to an individual company. A private cloud is either operated by the company itself or has outsourced its operation to a service provider. Hardware and software are either installed in the company’s own data center or in the data center of the service provider. The private cloud allows maximum control over the resources used and permits individual applications and services. The services are accessible either via the company network or via the Internet and virtual private networks (VPNs). A private cloud may become necessary if, for example, strict legal data protection regulations or security requirements prohibit outsourcing data and applications to an external service provider, or if very specific services are required.

What are Multi Cloud and Hybrid Cloud?

The two cloud models Multi Cloud and Hybrid Cloud play an increasingly important role. The Hybrid Cloud combines the services of a private and a public cloud. A joint cloud environment is created, whose services are obtained as required from a public or a private cloud. This allows the best of both worlds to be combined. The nine cloud navigators also support hybrid setups thanks to two of their own redundant data centers and the partnership with Google Cloud. Thanks to that nine can optimally support you in operating a hybrid setup.

A Multicloud is a combination of several public clouds from different providers. The provider with the best cloud offer can be selected for the services required. The Multicloud reduces dependency on individual providers and provides more redundancy.

Misunderstanding security

One of the biggest misconceptions about the public cloud is the security of the public cloud. It is claimed that a private cloud is automatically more secure than a public cloud. Looking at the details, this prejudice is difficult to prove. Although a private cloud is not available to the general public on the Internet, it is still connected to the Internet. Hackers can also find and attack a private cloud. Companies have complete data sovereignty in a private cloud but are responsible for the security of their cloud environment. Monitoring the private cloud, applying security patches, and fending off attacks requires a great deal of effort and expertise. If a company protects the private cloud insufficiently or lacks the necessary security know-how, it is vulnerable to attacks.

In terms of data protection, the public cloud offers a high level of security that can compete with a private cloud in many areas. Many public cloud providers give their customers the option of choosing the cloud location for service delivery. In addition, there is the option of comprehensive data encryption. Strict data protection and compliance requirements can be implemented. Certifications play a major role here, which is standard for the public cloud, whereas in the private cloud they relate only to the data center and not to the infrastructure brought by the customer.

Public Cloud: Typical use cases for companies

After so much theory, let’s look at some use cases. Below are three examples of typical use cases of a public cloud:

E-Commerce applications with dynamic resource requirements

Suppose your company is in the e-commerce business and runs an online shop with sales that are highly seasonal. Of course, you always want to offer your customers the same user and shopping experience. During the Christmas business, for example, your e-commerce systems should not have longer response times. If you operate the servers for your applications yourself, you must dimension them so that they are designed for peak loads. This means that the servers are only moderately loaded for most of the year. They waste resources and work inefficiently. When you use a public cloud, you can scale performance as needed. The services are elastic and can be easily expanded temporarily for the Christmas season. You only pay for the capacities actually booked and, compared with an oversized in-house IT infrastructure, significantly reduce your costs.

As a startup being immediately available worldwide 

For the success of a start-up, it is essential how quickly the company with its innovative business idea is available on the market (short time-to-market). However, a start-up in particular lacks the resources and an existing IT environment. There is simply no time and money to invest in hardware and software and to build up their own IT infrastructure. The public cloud offers a way out. The services of the public cloud are available worldwide immediately after booking. Globally distributed data centers ensure almost the same response times and performance in every corner of the world. The start-up company’s employees can take care of the further development of the business model without having to concern themselves with the operation or maintenance of the IT systems. This concentration on the core business and the demand-oriented provision of the required IT services by the public cloud provider increases the startup’s chances of success.

Provide redundancies for critical services

Another use case is the availability of redundancies for critical services. A company’s business processes often depend on a few applications or IT systems. A failure of a single server can quickly bring the entire company to shut down and cause immense loss of revenue. Providing redundant systems costs a lot of money and causes effort. In a public cloud, a second infrastructure can be provided, which can be activated in an emergency until the disaster recovery is complete and the original systems can be taken over again.

The advantages of the Public Cloud

  • no investments in own IT infrastructure necessary
  • transparent, usage-dependent costs
  • Minimum effort to operate and manage certain services – the provider installs, operates, maintains and monitors the hardware and software to deliver most services
  • Easy scaling and configuration of services via web-based user interfaces or APIs
  • fast availability of the booked services
  • Providers ensure high availability and security of applications, data, and services
  • Providers of a public cloud have a great deal of know-how for the secure operation of their IT – the most modern security concepts are implemented with corresponding certifications
  • access to the cloud services is possible everywhere via the public Internet

The Limits of the Public Cloud

A public cloud reaches its (local) limits when data requiring special protection, such as medical data, financial data, or legal data, are to be stored and processed. The public cloud is usually operated in certain regions, usually limited by national borders. This means that the public cloud can only be used within a certain area to which certain local laws and legal judgments apply. As a customer, it is important here to check with the cloud provider to ensure that they comply with local laws and other regulations (financial, medical, etc.).

Since several customers share the same cloud resources, it cannot always be 100% ruled out that performance or availability will influence each other. It is possible that not all the services you need are available. However, this should be seen in relation to the location and the possibilities of the respective public cloud: Since the public cloud generally has a larger scope and more technical resources, the availability of resources can be regarded as at least as good as in the private cloud.

The nine cloud navigators support you on your way to the public cloud

It is not always easy to select the right cloud for the individual requirements of a company. Private and public clouds offer specific advantages and disadvantages that need to be considered. In addition, with the Hybrid Cloud and the Multi Cloud, there are other cloud models that can represent suitable solutions depending on the applications to be implemented. 

In many cases, however, there is no way around the public cloud. It is a must for companies that need professional IT services but want to concentrate on their core business and do not want to waste resources on operating their own IT infrastructures. 

The nine cloud navigators help you on your way to the cloud. They are there to help you choose the right cloud environment – whether private cloud, hybrid cloud, public cloud, or the respective managed version. Together with you, we will find the optimal solution. 

Our cloud experts will be happy to answer your questions or introduce you to our managed public cloud solution based on the Google Kubernetes Engine.

The Road to the Cloud – What is Private Cloud?

Clouds are servers, or networks of servers, on which corporate applications or services are provided over the internet. Private cloud companies usually take care of infrastructure, server space, security, and application management themselves.

In a public cloud, companies are provided with a predefined selection of services via their data center and are not responsible for any of the management of their cloud hosting solution. The data is stored in the provider’s data center and the provider is responsible for the management and maintenance of the data center.

This relieves many companies enormously: They don’t have to operate cloud services in their own data center and save hardware and software resources as well as associated maintenance work.

Many companies rely on the private cloud to operate their own applications and hope to achieve better data protection standards than in the public cloud. But did you know that the private cloud is not automatically more secure than other cloud variants?

What are the features of the private cloud?

A private cloud promises exclusivity, i.e. only companies and their employees can access their applications themselves. Most companies operate not only standard solutions but in particular individual applications via a private cloud. They can also determine the server location when using a private cloud: As a rule, they operate the server either on their own premises or with a cloud service provider.

Control over the server location tends to make a private cloud more secure. Access paths provide additional security. Authorized users access the cloud services either directly via the company’s own network or via VPN connection. 

In many cases, companies are responsible for managing their private cloud themselves. They then take care of security aspects, updates, and ongoing server operation etc.. 

What advantages does the private cloud offer?

A private cloud not only provides exclusivity but also brings a number of other advantages:

  • Individuality: Companies retain control over their applications. The IT infrastructure of a private cloud is tailored to individual business processes. 
  • Flexibility: Customers can and usually must operate their private cloud with their own IT infrastructure. Here they can decide for themselves whether they want to update, expand, or scale it, for example. With a public cloud, the cloud provider specifies the services and their configuration options. 
  • Security: With a private cloud, companies retain control over their data, and also full control over the choice of security mechanisms. Private clouds cannot be accessed via public websites. Access is either via the company’s own intranet or with a VPN connection. Hackers, therefore, find it much more difficult to locate a private cloud.

One cloud – four variants

Depending on how much server space, IT skills or time resources companies have, there are various private cloud variants available. 

  1. Internal Private Cloud
    The name says it all: this form of private cloud is operated internally by companies. This means that companies operate a cloud system via their own IT infrastructure and servers in their own building.
  2. Hosted Private Cloud
    Companies do not operate this form of private cloud in their own data center. The provider takes care of this. The responsibility for updates, maintenance work, and security aspects remains with the customer
  3. Managed Private Cloud
    By operating  the cloud on their own IT infrastructure cloud providers relieve their customers of maintenance work and updates. Like nine, some providers also guarantee high-security standards and round-the-clock support.
  4. Community Private Cloud
    This variant is a special form of a private cloud where several companies access the cloud services. Typically, many companies opt for a community private cloud when they work on joint projects and use the same data and services.

Misconceptions about the private cloud

A private cloud does offer advantages. However, it also often causes misunderstandings. A private cloud is not automatically more secure than other cloud variants.

It does have the advantage that companies retain data sovereignty and the cloud is harder for hackers to find. But that doesn’t automatically mean greater data protection, because companies are responsible for security standards in the private cloud themselves. If they do not protect the cloud sufficiently, they are correspondingly vulnerable to attacks.

These and other challenges should be kept in mind:

  • The private cloud is also on the Internet. Even if it is harder to find – it is to be found.
  • There are only a few service providers that offer good support for a private cloud. Companies may face a long search in this regard. 
  • If the data center’s servers go down, the private cloud services also come to a standstill. You can avoid this by spreading them across multiple data centers. However, this will incur higher costs.
  • A private cloud is not something that companies can provide globally to all employees. They first need the right IT infrastructure. 

For whom is private cloud suitable?

Many companies operate extensive and complex applications, e-shops, or customer and information portals. 

The private cloud is particularly suitable for handling sensitive data. Companies for whom this is of interest are, for example, companies from the healthcare industry. These companies work with health data and are required by law to strictly protect all data. Companies in this sector are themselves responsible for protecting their own data and that of their patients and often operate a private cloud in order to meet this obligation.

Home office and web solutions designed for communication between different locations can also be provided with individual cloud services. With a private cloud, companies can ensure high-security standards and simple but protected access for employees to applications and data. Even outside of their local workplace. 

Companies with particularly critical data often have their own solutions in the form of the internal private cloud. They have their own servers, their own IT infrastructure, and corresponding know-how. Therefore, the complete control and individual design of the cloud solution, but also the risk of failure and the need for external protection lies directly with them.

Companies that secure their data well, but do not (yet) have servers or IT infrastructure, often consider a public cloud solution in addition to the private cloud. The latter is usually associated with lower costs and also offers the advantage of being able to benefit from infrastructure improvements and updates without having to develop them themselves. Another solution is to outsource the applications to the private cloud of an external hoster and have them partly managed by the cloud service provider. Here, hardware management and cloud management are outsourced or the expertise of a cloud service provider is purchased.

Tip: It is important here to agree exactly which services the hoster is responsible for and for which the company itself must provide solutions. Updates are a particularly relevant topic here. It is best to clarify these questions right at the beginning.  

A private cloud is suitable for many scenarios.specially for companies that already have their own know-how and IT structures and want to benefit from customizable cloud services.

Private cloud or not? – The nine cloud navigators help with the decision

Which cloud solution is best for a company is not always obvious at first glance. On the way to the cloud, the situation of the company must always be considered: Costs, resources, know-how, existing structures, and of course the intended applications and data to be stored must be taken into account in finding the best cloud solution.

As your cloud navigators, we at nine are happy to accompany you on your way to the cloud: We advise you from the start and work with you to find the right solution.

If you have any further questions about the private cloud or alternative cloud solutions, please contact the Nine cloud navigators.

Review of our Google Cloud Zürich Meetup #4

The Google Cloud Meetup #4 took place on 19 May 2020 for the first time on Google Meet. In Switzerland, it is currently still not allowed to meet with more than 5 people. Even though we couldn’t offer Pizza and Beer, we were able to have 40 people listening to our two topics.

Thomas Hug, CEO of nine introduces the speakers Jakob Ehrl of Google Cloud and Cyrill Troxler & Sebastian Nickel of Nine Internet Solutions AG. 

From Containers to Serverless with Cloud Run

Jakob Ehrl, Customer Engineer of Google Cloud Zürich, introduced us into his sandbox experiment with Cloud Run. Due to the current home office situation, he can’t travel to Google’s offices in Zürich by bike (15km). Together with his girlfriend, he decided to run every second day and log the activities to Strava. In order to play around with the gathered data, he shows in his uncommon painted presentation and lots of interaction with the audience, how the GPS data points from his watch get into BigQuery where he can analyze them. He presents a pipeline of entirely serverless building blocks including

  • Google Cloud Storage (ingress and intermediate processing results)
  • PubSub (for service communication)
  • Cloud Run (for parsing the input data in a given Java application)
  • Cloud Functions (as an alternative to Cloud Run)
  • BigQuery (as data warehouse)
  • Data Studio (for visualization)

He said it took him about a week to put the things together by mostly clicking on the Google Cloud Console – without counting the nights!

Typical Kubernetes User Questions

(The numbers in brackets refer to mm:ss in the recording below)

The 45min Q&A session about typical Kubernetes user questions with nine Kubernetes Engineers Sebastian Nickel and Cyrill Troxler started with survey questions. It showed that most of the attendees already have Kubernetes experience or are evaluating Kubernetes. They are using Raspberry Pi Clusters, Kube Flow or Minikube to mention a few.

  • (3:05) What are the best practices making services “elastic” to scale up and down automatically?
  • (5:05) What are the experiences with preemptible nodes with GKE?
  • (8:20) What is the best way to create resources in Kubernetes?
  • (11:48) What about vertical scaling nodes?
  • (13:23) Do you work with customer resource definition?
  • (13:38) Why do you not use StackDriver for logging?
  • (17:22) How to backup the Kubernetes cluster? What are your experiences with persistent volumes and backup?
  • (19:13) Do you have hints or experiences in config pod eviction policies?
  • (20:20) How to create/use infrastructure around Kubernetes in the cloud (databases, caches, etc.)?
  • (21:58) You don’t use databases within Kubernetes?
  • (22:50) What/how should we monitor in Kubernetes?
  • (24:50) Do you monitor outside Google infrastructure?
  • (26:15) Do you provide a cost driven approach to your customers or are they just paying for Google Cloud resources?
  • (27:10) How do you make sure that the load is equally distributed between zones?
  • (29:40) Do you have customers with hybrid setups? What about VPNs with i.e. 3 GBits of traffic?
  • (33:52) How is kubectl pronounced?
  • (34:52) Is Kubernetes secure?
  • (38:23) Is it hard to run an own Kubernetes cluster like an on premises one?

Good starting points for GKE for people starting from zero are https://cloud.google.com/kubernetes-engine/docs/tutorials or https://www.coursera.org/learn/gcp-fundamentals 

Further outlook with the new online experience

Our next Google Cloud Meetup is planned for August 25, 2020 – hopefully in Zürich City again. With the very good experience doing an event online, but the lack of networking capabilities at the end, we want to combine the advantages of both, online and offline, as soon as it is allowed again. If you have an interesting project running on Google Cloud and think it could be interesting for others, feel free to contact us! We also very much appreciate suggestions for topics and possible speakers, by either meet-up-message, by using the contact form on our website, or via email to one of your contacts here at nine. We would like to keep things exciting. We look forward to seeing you again!

The Meetup link to the next Google Cloud Meetup #5 on August 25, 2020 (https://www.meetup.com/de-DE/google-cloud-zuerich/events/270878484/)

Talk to one of our experts

Do you have any questions about our products? Either contact Sales or go directly to your cockpit to see all the possibilities at Nine.