Miniconf on Cloud Server Management (Chennai)

On costs, scaling and securing cloud servers

About the event

Cloud server management brings with it as many challenges as it offers conveniences. It is time to unbundle questions about:

  1. Resource allocation: how best to allocate manpower, time, money and infrastructure capacity?
  2. Scaling: how best to utilize capacity in the present, and factors involved in planning for the future?
  3. Security: which scenarios must you plan for, and how best to secure your data, applications and systems?

Who should submit a talk

If you:

  1. Work with cloud servers,
  2. Plan and manage infrastructure,
  3. Make decisions on technology and architecture for your organization,

submit a talk for any of the three events in this series.

Format

Each event is single-day, with about 4-5 short and long talks, 2-3 demos, one BOF, and a three-hour workshop on configuration management.

We are accepting proposals for:

  • 30-minute talks – which cover conceptual topics and case studies.
  • Crisp 15-minute talks – on new tools and techniques in cloud server management.
  • 5-10 min demos.
  • Birds of Feather (BOF) sessions, led by 1-3 persons from the community, on a relevant topic.
  • 3-hour hands-on workshops on configuration management.

Selection process

Proposals will be shortlisted and reviewed by an editorial team consisting of practitioners from the community. Make sure your abstract contains the following information:

  1. Key insights you will present, or takeaways for the audience.
  2. Overall flow of the content.

You must submit links to videos of talks you have delivered in the past, or record and upload a two-min self-recorded video explaining what your talk is about, and why is it relevant for this event.

Also consider submitting links to:

  1. A detailed outline, or
  2. Mindmap, explaining the structure of the talk, or
  3. Draft slides

along with your proposal.

Honorarium for selected speakers; travel grants

Selected speakers and workshop instructors will receive an honorarium of Rs. 3,000 each, at the end of their talk. Confirmed speakers and instructors also get a pass to the conference and networking dinner. We do not provide free passes for speakers’ colleagues and spouses.

Travel grants are available for domestic speakers. We evaluate each case on its merits, giving preference to women, people of non-binary gender, and Africans.
If you require a grant, request it when you submit your proposal in the field where you add your location. Rootconf Miniconf is funded through ticket purchases and sponsorships; travel grant budgets vary.

Important dates

Cloud Sever Management Miniconf in Chennai: 25 November, 2017
Cloud Sever Management Miniconf in Mumbai: 8 December, 2017
Cloud Sever Management Miniconf in Delhi: 9 December, 2017

Contact details:

For more information about speaking, Rootconf, the Miniconf series, sponsorships, tickets, or any other information contact support@hasgeek.com or call 7676332020.

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more

Srinivasan Rangarajan

@cnu

The rocky road from monolithic to microservices architecture

Submitted Oct 27, 2017

Delivering Artificial Intelligence/Machine Learning products at scale is hard, especially when each user wants a personalized experience.
Vue.ai is an AI Platform which has different products built on top of it to automate the retail domain. It started out as a non-scalable prototype with a small set of features and grew to the current version with multiple microservices serving millions of users every day.

Today, there are separate microservices to handle catalog ingestion, image processing, image search, apply ML models on user event data (page view, buy, add to cart) and serve personalized results via REST APIs.
During the process of building this platform we learnt a lot of lessons, including where to use asynchronous vs synchronous, why caching can’t help you everytime, and why you should always have immutable microservices.

Outline

When it was a monolithic architecture, we used the EC2 servers as plain linux boxes without any ability to automatically scale. One of the main advantages we got out of the rearchitecture is the use of multiple managed services available in AWS and the stability. We also made sure things can scale and we started using cost effective components like serverless lambda functions, docker containers, etc.

  1. Introduction
  2. Explanation about the monolithic v0.1
    a. Problems we faced
  3. Microservices and how it all ties together
    1. Advantages, including how personalization is now possible.
    2. Mistakes we made, especially in infra/resource allocation.
    3. Improvements that are still needed.
  4. Things to remember when you make the shift to microservices.

Speaker bio

Srini has been helping startups build scalable and distributed systems for the past 10+ years. Currently he is scaling AI to millions of retail consumers all over the world by making sure the Engineering team builds and delivers the best AI products at Mad Street Den.

Links

Comments

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

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

{{ errorMsg }}

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

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more