Skip to main content

Dangling references

I picked up my data structures book and started reading it. First thing that came to my mind is, If I were a teacher, how would I explain to students on pointer concepts. Believe me, it is still a challenging concept to comprehend.
Pointer is a like a phone number to reach a person. Pointer points to address of the object that holds the data. Now, what is dangling reference. It is possible that there can be many pointer variables pointing to same address. For example, You, myself, someone else can have the same phone number of the person to reach. Question: What if the person dies? :) I still will have phone number, but cannot reach him or her. On top of that, what if that phone number gets assigned to some other person. In that case, I will reach the wrong person. The phone number I have is a dangling reference. Pointer pointing to the address, but address does not hold the desired object anymore ...

Simple, isnt it?

Comments

Popular posts from this blog

Essential GCP services for a new age application

Identity and resource management IAM  Identity aware proxy Resource Manager Stackdriver Monitoring Stackdriver Monitoring: Infrastructure and application monitoring Stackdriver Logging: Centralized logging Stackdriver Error Reporting: Application error reporting Stackdriver Trace: Application performance insights (latency) Stackdriver Debugger: Live production debugging Development management Cloud Deployment Manager: Templated Infrastructure deployment Cloud Console: Web based management console Cloud shell: Browser based terminal/CLI Development tools Cloud SDK: CLI for GCP Container registry: Private container registry Container builder: Build/Package container artifacts Cloud source repository: Hosted private git repository Database services Cloud SQL: Managed MySQL and PostgreSQL Cloud BigTable: HBase compatible non-relational DB Cloud Datastore: Horizontally scalable non-relational (ACID) Cloud Spanner: Horizontally scalable relation...

GCP - BigQuery Roles

GCP BigQuery Roles (Quick view)

Cloud Architecture consideration

Thorough understanding of cloud architecture and Google technology Understand business objectives; Strategize cloud solution design inline with archtiecture best practices Design and Develop Manage robust, secure, scalable, highly available and dynamic solutions Proficient with multi-tiered distributed application - multi-cloud and hybrid environments Designing and Planning a cloud solution architecture - Business use cses - Product strategy - Cost optimization - Supporting application design - Data movement - Trade-offs - Build, buy or modify decisions - KPI and ROI metrics - Compliance and observability - HA and fail-over design - Elasticity - Scalability to meet growth requirements - Network integrations - Native networking - VPC peering, firewalls, container networking - Identifying data processing pipeline - Matching characteristics of storage systems - Data flow diagrams - Storage system structure - Mapping compute needs to platform products - License map...