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 email@example.com or call +91 76763 32020.
Note: We aren’t accepting any new talks.
Modular-services in a Nodejs Monolith
Microservices are described as services with a few hundred lines of code. Big organizations run such micro services in 100’s and are often looked up to by engineers in startups/smaller companies, too eager to join that league. However the hard reality is that only a few startups will survive to scale and need micro services. Busting the hype, the experts are suggesting smaller companies to adopt writing modular code instead of microservices code. How do you write modular code in NodeJs and why are they better than microservices?
Modules are blocks of functionality that are bigger than micro services, a few files ideally. A few modules can be piped/joined together to make an app. They share a lot of similarities to micro services and hence to title — modular services in a monolith. A well written modular code can be broken up into microservices (when being deployed) and also tested upon as a single app (when running on a laptop). I will introduce a dependency chaining library ArchieJs (https://github.com/archiejs) and how the modules in ArchieJs are the way to architect your Nodejs monolith.
Other recent developments outside of NodeJS world on this topic is inclusion of ‘module’ construct in Java 9. The first part of this talk is inspired by similar talks from Java world. The second part ventures into implementing the modular architecture tenets in the Js world.
- Compare Modular Monoliths to Microservices - engineering complexity, cost, etc
- Introduction to Tenets of Modular development
- Using Archiejs to implement Modular architecture
- Challenges to splitting monoliths into services; and how Archiejs addresses them
PS... I can alternatively do a crisp talk also.
I have been building nodejs applications for many years and have built mostly monoliths or worked in SOA environments. I started using a library - architect.js in 2013 and have written a lot of code following the modular pattern. I am reusing code from the modules I wrote in 2013-14 in a project I am working on these days. Another of my recent interesting app is www.halfchess.com (a variation of chess).
- The below blog consists of some code level discussions I recently had with a CTO of LuxGroup (Australia).
- Archiejs docs