Skip to main content

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 mapping
- Network and management planning
- Managing systems and data to support solution
- Integrating with the existing systems
- Building Proof of concept
- Future solution improvement consideration
- Evaluate business needs
- Evagelize and advocate improvements

Managing and provisioning solution infra
- Extend GCP
- Multi-cloud integration
- Security
- Data protection

Designing for security and compliance
- IAM
- Resource hierarchy
- Data security (Key management, encryption)
- Pen testing
- Separation of duties (Different project teams)
- Security controls
- Managing customer supplied encryption keys with cloud KMS
- Audits (External and Internal)
- Certification

Managing implementation
- Application development
- API Best practices
- Interacting with GCP

Analyze and Optimize technical and business processes
- CI/CD
- BCP and DR

Solution and Operations reliability
- Monitoring, Logging, Alerting
- Deployment and release management (Blue-Green, Canary, Fail-over cutovers)
- Operational troubleshooting
- Quality control measure

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