Skip to main content

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 relational DB

Bigdata analytics services

  • BigQuery: DW
  • Dataflow: Stream or Batch data processing
  • Dataproc: Managed Spark/Hadoop
  • Dataprep: Transform/Clean Raw data
  • Pub/Sub: Global real time messaging

Storage services

  • Cloud storage: Object storage and serving
  • Nearline: Archival, once in a month
  • Coldline: Archival, once in an year (DR option)
  • Persistent disk: VM disks

Data transfer services

  • Transfer appliance: Hardware for data migration
  • Storage transfer service: Cloud to GCP data migration

Compute services

  • Compute engine: VMs
  • App Engine: Managed platform
  • GKE: Managed K8S
  • Cloud functions

Network services

  • VPC: Software defined networking
  • Load balancing: Multi-region load distribution
  • Dedicated Interconnect: Dedicated connection for extended networking
  • IPSec VPN: Low cost GCP extension over public internet








Comments

Post a Comment

Thanks for your comments.

Popular posts from this blog

Key to adopt open source product

Friends, I am working on business solution implementation on open source product called Kaltura. Kaltura is a media management solution and has loads of features that compel any business to take a peek into it. More-over this is the only complete end-to-end open source software available to handle digital assets. But it comes with its own head ache. Considering its open source, its understandable. I feel, handling these would ensure you the success in your open source product implementation. 1. In my opinion, before adopting any open source software, build the capability to deal with the inconsistency bundled in the open source software. 2. I would avoid involving external consultants for 2 reasons.      a. I am not sure, they would bring necessary expertise on to table      b. I fear that there would be little ownership, they will not see big picture of my business (neither I am interested to share it all) 3. Alternative to that is to build the tea...
1 comment
Read more

Secure your application on cloud

Handling sensitive data Define sensitive data for your application. Classify as sensitive data and confidential data. Sensitive data is something like password, credit card account number, something that you should not compromise at all. Confidential data could be your customer’s health record, something that requires your permission before its usage. So, you need to define sensitive data in the context of your application. There are many ways to protect the sensitive data in transit; the easiest way is to use SSL. This is nothing different than handling sensitive data in any traditional application.   However, make sure you apply this rule while designing your application for cloud deployment. Alternatively, you can encrypt the sensitive data and transport. Be noted that any kind of protection you design, will have implications on performance. However this is ignorable considering the nature of sensitive data. If you just want to protect your data from being tampered du...
Post a Comment
Read more

Object orientation and Service orientation

Object orientation is all about modeling the real world information mainly through encapsulation, abstraction, polymorphism, containment, inheritance and so on. In simple words, an object contains the data structures and methods to change the content state. A typical OO run-time manages the life cycle of objects. You can create as many objects as required as long as the run-time does not over run its memory. Service orientation requires you to encapsulate a process. The operations of a services are interaction points with the particular process. Data structures are the arguments for these operations. Service run-time shall validate the correctness of the process. Service can have multiple invocation instances, not multiple instances of service itself. Example: TrainTicketBookingService involves a process. - Check the train timings //  interaction point - Check the seat availability // interaction point - Issue ticket // interaction point There could be many ticket...
Post a Comment
Read more