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

Aarthi K

@aarthi-k

NorthStar - Monitoring Microservices using Go

Submitted Nov 8, 2017

As we move from a huge monolithic architecture to distributed microservices architecture, it gets more difficult to maintain the performance of each microservice and communication between the microservices.

Each microservice is has it’s own API and a set of standards. A change in one can break another. Generally, this is not caught until it goes to production and something breaks and someone complains about it. By then, there has already been a downtime recorded.

NorthStar provides a bird’s eye view from which you can know how your application is performing and helps you catch failures before your customers do. NorthStar is written in Go and uses Swagger files.

This talk will cover how we built a scalable, high performance system using Go and is intended to provide insight to anyone building a webservice on how to effectively monitor it.

Outline

This talk is around how we built a service which can continuously test and monitor your system from the outside.

  1. Conventional Monitoring
    a. Where does it Fail
  2. How does NorthStar work?
  3. Why Go?
  4. Performance - Goroutines & Channels
  5. Fault Tolerance - Contexts
  6. Improvements

Speaker bio

Aarthi is a Product developer working for the Platforms Team at Freshworks and has worked on a highly scalable real time servicing system using Go. She has also developed NorthStar from the ground up with Go.
When she is not coding at work, she is either reading Jeffrey Archer or trying to cover the huge backlog of articles on Pocket.

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