Design patterns for cloud architecture
Rootconf For members

Design patterns for cloud architecture

Exploring trends which influence business and strategic decisions around cloud computing.

Make a submission

Accepting submissions till 30 Jun 2023, 10:00 PM

Tickets

Loading…

Design patterns for Cloud Architecture - key challenges

Cloud computing is not just about “closing down data centers” or about “efficient storage and compute resources”. The year-on-year growth in cloud computing adoption has brought about unique and innovative approaches - in the design of IT architecture; the generation, storage and retrieval of data; and redesign of business processes.

Design patterns for Cloud Architecture explores the current and emerging trends across the range of attributes which influence business and strategic decisions around cloud computing. Experts will highlight the topics which dominate any discussion around cloud computing including governance and management of data, edge computing and the economics of cloud computing.

Takeaways for participants

Engage with experts who will discuss the following topics:

  • Designing IT systems for emerging aspects of cloud computing.
  • Securing data in the cloud.
  • Audits and regulatory compliance in public cloud computing.
  • Digital Forensics and Incident Response (DFIR) in public cloud.
  • Public cloud economic models - designing for efficient usage and cost optimization.

Who should participate

  • Software/IT architects
  • Network security specialists
  • Solution Architects
  • Developers adopting low-code/no-code models
  • Product Managers
  • Technology reporters

Talks, forum and in-person conference

RSVP to participate. This project consists of talks, forum and in-person events. Check the schedule to stay updated. Talks held between in-person conferences are online unless specifically mentioned.

Purchase a subscription to access videos and to support Rootconf’s community activities.

Code of Conduct: Hasgeek’s Code of Conduct applies to all participants and speakers.

COVID protocols and masking policy: In keeping with COVID protocols, the following is applicable to all participants:

  1. Participants attending the meetups in person must keep their vaccination certificates handy. The venue may ask you to show your vaccination certificate as proof of being fully vaccinated.
  2. Wearing masks is optional.

Contact information: For queries about Rootconf or this track, contact Hasgeek at info@hasgeek.com or call (91)7676332020.

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Supported by

Promoted

March conference theme - optimizing the costs of cloud infrastructure.

Submitted Feb 3, 2023

Cloud is expensive. So are microwave ovens. i.e. if you keep them running even when you don’t need them.

  • K8s promises to address this by providing a framework for capacity management.
  • But promise doesn’t translate to actual cost savings.
  • Capacity planning is a hard problem and continues to be even with K8s (albeit a little less hard).

Most cloud costs are inflated and to have a meaningful impact on your $$, you need to have leverage to negotiate the price list.

  • Identify the largest contributors towards your $$.
  • Do capacity and data modeling.
  • Negotiate hard.
  • This one thing will have the most significant impact on your spend.

Lost opportunity cost.

  • Quick turnaround for business/product requirements possible on cloud.
  • Faster MVPs translate to faster iterations and thereby better dev productivity without having to worry about infrastructure plumbing
    Cloud enables such use cases seamlessly
    Catch:
    • It is important to realize that these MVPs may not be most cost optimal and built and designed solely for the purpose of unblocking a business opportunity that far outweighs the $$ spent on technology powering it.
    • Define the pivot point wherein MVPs will need to graduate to something that addresses these concerns.

Cost of moving out when things go wrong.

  • Costs associated with Cloud are not just $$$ on the invoice, but debt companies incur in building dependencies on one cloud/only cloud.
  • Imagine your cloud provider having a massive outage/negotiations fall through/anything else that makes you want to change.
  • But your orchestration is so hard wired that you don’t have a choice and are at the other party’s mercy. At that point you pay whatever’s the price ($$, reputation, inefficiencies).
  • Multicloud/hybrid clouds shouldn’t be an afterthought but a design goal.

Comments

{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Make a submission

Accepting submissions till 30 Jun 2023, 10:00 PM

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Supported by

Promoted