##About Rootconf 2019:
The seventh edition of Rootconf is a two-track conference with:
- Security talks and tutorials in audi 1 and 2 on 21 June.
- Talks on DevOps, distributed systems and SRE in audi 1 and audi 2 on 22 June.
##Topics and schedule:
View full schedule here: https://hasgeek.com/rootconf/2019/schedule
Rootconf 2019 includes talks and Birds of Feather (BOF) sessions on:
- OSINT and its applications
- Key management, encryption and its costs
- Running a bug bounty programme in your organization
- PolarDB architecture as Cloud Native Architecture, developed by Alibaba Cloud
- SRE and running distributed teams
- Routing security
- Log analytics
- Enabling SRE via automated feedback loops
- TOR for DevOps
##Who should attend Rootconf?
- DevOps programmers
- DevOps leads
- Systems engineers
- Infrastructure security professionals and experts
- DevSecOps teams
- Cloud service providers
- Companies with heavy cloud usage
- Providers of the pieces on which an organization’s IT infrastructure runs -- monitoring, log management, alerting, etc
- Organizations dealing with large network systems where data must be protected
- VPs of engineering
- Engineering managers looking to optimize infrastructure and teams
For information about Rootconf and bulk ticket purchases, contact email@example.com or call 7676332020. Only community sponsorships available.
##Rootconf 2019 sponsors:
Art and science of choices in engineering
What’re the factors to consider when we make an engineering choice in tools/infra and how to evaluate the cost vs benefit of it.
How’s the choice usually made? What’re the several factors involved?
Do you really have a problem the tool is solving or the tool is making us think you’ve a problem.. how to find out if you’ve the problem or going to face it later.
The cost breakup of all elements:
Benefits of the tool >> Time to decide + cost (Engineering) + Cost (Operations/maintenance) + Cost (Infrastructure) + Cost (cultural drift)+etc.
How much percentage of cost is acceptable for the benefit.
Idenfifying elements unique to your company, that contribute to overall decision.
We’re going to deal with cost factor involved in choice of tools we adapt or build.
Total cost of adapting a tool = Cost (Engineering + Infrastructure + Operations + Service + Culture change)
cost ( Infrastructure ) = straight forward.. may be map it to your cloud bills or so.
cost ( Service ) = maintenance + management.. like every *aas out there, internal tools also require attention and service.
cost ( Engineering ) = Average num of days it takes developers
*their average salary
*number of engineers for this project + coolness cost - tool familiarity + Estimation error + Research cost + Training cost
cost ( Culture change) = This is hard to calculate in terms of numbers. You can measure how long did it take to bring everyone on same page. The length of meetings, time taken to decide an approach, the way a decision is made (was it with disagreements, setbacks, etc.) are some pointers.
Benefits = cost ( Engineering time saved due to the tool + Increase in revenue )
Important aspects to consider:
- This is a non-exhaustive list. There are several other factors applicable to your company.
- Take approximations when it comes to cost (culture change or human emotions)
- The solution offered by the tool, does the problem exist or you started to think you’ve this problem only after reading a blog post or such?
- Calculate it for long term.. may be, for 5 years ahead.. make a decision based on the cumulative.
Devops at webengage. We do optimisations quite frequently with cost in mind and adapt various practices+tools in order to acheive the same. I handle 40+ microservices at a scale of few services being at 100k requests per second.