In today’s technology world, operational efficiency is pivotal. It is time to focus on measuring, learning and improving different aspects of infrastructure scaling and development cycles. Not to forget the the culture of DevOps and team dynamics.
Rootconf 2015 focuses on four key aspects of DevOps and scaling infrastructure: virtualization, managing infrastructure at scale, new technologies, and team management.
- Rootconf is aimed at DevOps, CTOs, and teams and companies.
- Organizations developing a Continuous Integration and Continous Deployment strategy. You will get a headstart by attending Rootconf.
- Managing infrastructure at scale:
- Scaling processes for enterprises – log monitoring, security, data management.
- Scaling tools for enterprises – such as using Graphite, logstash and other tools at scale.
- Upcoming technologies such as Salt.
- Team management / DevOps as culture.
This year’s edition spans two days of hands-on and conference. We are inviting proposals for:
- Full-length 40 minute talks.
- Crisp 15-minute talks.
- Sponsored sessions, 40 minute duration.
- Hands-on Workshop sessions, 3 hour duration
Proposals will be filtered and shortlisted by an Editorial Panel. We urge you to add links to videos / slide decks when submitting proposals. This will help us understand your past speaking experience. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals.
Proposers must submit presentation drafts as part of the selection process to ensure that the talk is in line with the theme of the conference, and to help the editorial panel build a strong line-up for the event.
We will notify you about the status of your proposal within two weeks of submission.
There is only one speaker per session. Entry is free for selected speakers. As our budget is limited, we will prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek will provide a bursary to cover part of your travel and accommodation in Bangalore. Bursaries are limited and made available to speakers delivering full sessions (40 minutes or longer).
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like it to be available under a permissive open source license. If your software is commercially licensed or available under a combination of commercial and restrictive open source licenses (such as the various forms of the GPL), please consider picking up a sponsorship. We recognize that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.
Last date for submitting proposals: 15th April
Shortlisting process: 31st March onwards
Pre-conference workshops: 13th and 14th May
Conference dates: 15th and 16th May
Rootconf will be held in the MLR Convention Centre, J P Nagar.
For more information about speaking proposals, tickets and sponsorships, contact firstname.lastname@example.org or call +91-7676332020.
Build your own Dynamic CDN
Build your own Dynamic CDN which can handle more than 10K reqs/sec per node
Yeah, like Akamai CDN or AWS Cloudfront.
So what’s the difference?
Serve dynamic content and not just static HTML, JS, images or CSS files.
Wait! It does not make sense.
Join me while I explain how and why we did it @Wingify and maybe then it starts making sense!
We at Wingify started facing issues with our dynamic content serving layer when our servers (using
nginx + varnish + php) were serving around
1K reqs/sec. That is when we built our own dynamic CDN.
Different servers across the world remain in-sync with each other to serve dynamic content based on originating URL and behavior of the visitor. The new infrastructre can handle more than
10K reqs/sec per node. These nodes can be present in any part of the world making it possible to scale horizontally as compared to
1K reqs/sec from around 32 nodes all sitting at one place.
With the new infrastructure we not only decreased the server count by more than
1/4th (read fewer sleepless nights) but also improved the average global response time by more than
Would be sharing how and why we did it, why the available CDNs did not work for us, and why is it easy to build one.
Hacker and a security enthusiast who believes in The Matrix. I love to optimize webpages and strongly believe that load-time is money when it comes to webpages. Working @Wingify as a Software Lead helps me in living my dream of solving interesting problems related to scale, load and optimizations.