Theme this year: The broad theme this year is going to be Building Reliable Web Apps. Please refer to the Topics section below for the subject of talks and workshops we are looking for.
We are inviting proposals for:
Full-length 40 minute talks.
Crisp 15 minute talks.
Sponsored sessions, of 15 minutes and 40 minutes duration (limited slots available; subject to editorial scrutiny and approval).
Hands-on Workshop sessions, 3 and 6 hour duration.
Proposals will be filtered and shortlisted by an Editorial Panel. Please make sure to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience and delivery style. 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. We might contact you to ask if you’d like to repost your content on the official conference blog.
We expect you to submit an outline of your proposed talk – either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.
You can check back on this page for the status of your proposal. We will notify you if we either move your proposal to the next round or if we reject it. Selected speakers must participate in one or two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.
A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.
There is only one speaker per session. Entry is free for selected speakers. As our budget is limited, we prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek provides these limited grants where applicable: two international travel and accommodation grants, three domestic travel and accommodation grants. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer). Speaker travel grants will be given in order of preference to students, women, persons of non-binary genders, and individuals for Asia and Africa first.
Updated (19 April 2017): We are currently looking for talks in the following topics:
Testing: Testing tools and strategies; test driven development and testing culture; continuous integration and testing workflows; and case studies around testing your application.
Performance optimization: Performance analysis tools and techniques; best practices for building performant applications; browser, NodeJS, and framework internals; network protocols; and performance case studies.
Crash and performance monitoring: Monitoring applications for crashes and performance issues while in production.
##Commitment to open source
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 for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise 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”.
Deadline for submitting proposals: 15 June 2017
**Conference dates: ** 15–16 September 2017
For more information about speaking proposals, tickets and sponsorships, contact firstname.lastname@example.org or call +91 76763 32020.
Note: We aren’t accepting any new talks.
Transition from Monolithic to Microservices Architecture
Most of the current web apps follow Monolithic Architecture i.e. all code (presentation, business and data access layer) is maintained within the same code base.
A micro service is something which is self-contained, well-defined and does not depend on the state of other services. It is a small, independently deployable unit.
So the idea is to explain what are the issues, including performamce, that can happen with a growing monlithic application and how to overcome it using microservices.
Why do we need Micro-services?
Performance challenges for growing monolithic application and other shortcomings
Solution: Micro services ?
Transition to Microservices
Technical impact of solution used
Understanding of how Monolithic application works
Mayank is a full-stack developer, with extensive Node.js projects under his hat. He is highly skilled in Node.js, Express, AngularJS, Meteor, PHP (Zend 1 & 2), MySQL, MongoDB, jQuery Google Maps. He is currently part of NodeXperts.
In his free time, he prefers to save humanity/other races, from the jaws of tyrants, with help of his computer and grit. He is a fan of WWE.
- GitHub: https://github.com/mayank-awasthi
- LinkedIn: https://www.linkedin.com/in/mayank-awasthi-b62a0724/
- Facebook: https://www.facebook.com/mayank.lucky
- Blog: http://nodexperts.com/blog/microservice-vs-monolithic/
- StackOverFlow: http://stackoverflow.com/users/1371636/mayank-awasthi
- YouTube: https://www.youtube.com/watch?v=aip5k8AXBJo