Let's define the "Fundamental Concepts" for Cloud Infrastructure | C2C Community

Let's define the "Fundamental Concepts" for Cloud Infrastructure

  • 26 January 2021
  • 4 replies

Userlevel 7

Our community is a diverse mix of customers and cloud practitioners of all experience levels with both Google Cloud but also cloud infrastructure. We have experienced pros leading and innovating in this space, as well as students and new customers just getting started. 

Over time, we hope to cover cloud infrastructure with content and conversations from every angle and experience level. To do so, we’ve identified this idea of “fundamental concepts” as a project for us all to collaborate on. 


When you hear Cloud Infrastructure, what are the first concepts you think of?

What technology concepts? What strategies or approaches?

What terms? 

What business processes? 

Which products? 

What are 3-5 areas of focus you would recommend to someone getting started?


Together, we can identify a community-vetted list of the fundamentals. From there, we can build resource lists, tutorials, explainer articles, and content plans to cover all the “must have” topics. 

4 replies

Userlevel 1

What technology concepts? What strategies or approaches?
Concepts: API driven orchestration of components, scaling (up/down) proportionately to match rise/fall in demand of services, stateful v stateless application, Data types and storage requirements, Distributed networking, compliance and security, Data Analytics

Strategies:  Cloud Deployment Manager/Terraform, Managed services for various data types & forms. 
Lift and shift and then Transform in the cloud, use various networking services to improve latency of traffic from customers reaching your applications/services hosted in the cloud, Start simple and expand later with adopting more and more GCP services. 

What terms? 
Configuration as data, Repeatable/Reproducible, Agile, Secure, Zero Trust Security Paradigm, CI/CD, 
Data Warehouse, Data Lakes, ETL

What business processes? Access management, Billing, Telemetry, Security , Audit & Compliance, 
Cloud Resource/Project Lifecycle Management.

Which products? GCE, GKE, GAE, Cloud Storage, Pub/Sub, BigQuery, CloudSQL, Firestore

What are 3-5 areas of focus you would recommend to someone getting started? 
A general purpose programming language expertise,  IAM, Cloud Storage & Networking, Containerization, some knowledge of data types & matching backends for them.  


Userlevel 7
Badge +65

For me, when I hear about Infrastructure, the first thing that comes to my mind is: What is my role?

Am I the Architect? If yes, then I have to Plan and Design with scalability in mind the project with the needs of the client (Business requirements). Then I have to build and deploy it (Technical requirements). The Cloud Infrastructure depends on these requirements.

Am I a Data Engineer? Then, for me, Cloud Infrastructure is the place where I have to work and create my pipelines. If there is an Architect, I will work on the Infrastructure he has created and modify it if necessary. Otherwise, I have to create it.

Am I the Security or the Network Engineer? How can I have the most secure infrastructure? Do I have the best networking?

And of course, I will include all of the above written by @Kartik  and much more.

Userlevel 6
Badge +12

I love this question...excited to see where the infrastructure connect group takes this over time. Not much to add as I am not an architect or infrastructure guy myself, but learning a lot in the process reading great posts like @Kartik’s and @ilias’s. 


Userlevel 7
Badge +65

Today’s France event was all about FinOps @JBranham.

@guillaume blaquiere told us about the cost of using or misusing the cloud infrastructure and how we can avoid unnecessary billing or how to keep it as low as possible. 

At least this is what I understood with my, not so good, French. :grinning: