See what’s under the hood at NextGenCatalogs

Hey Folks,

From the time Vikram published a post on TRH to seek feedback for NextGenCatalogs, we’ve received a lot constructive comments on our product vision and roadmap.  Thank you for that!!

Since then both Aaron and I have received a lot of requests from fellow tech-preneurs on sharing more about how we’re enabling SMEs to have product centric conversations with each other.

I’ve always believed in giving back to the tech community, and below is a primer on how we’re building NextGenCatalogs. Do try out the app, and let us know your feedback (I’m sure you’ll have some) 🙂

Below was originally posted on https://blog.nextgencatalogs.com/

Regards,

Gaurav

**************

Its been a great time developing the most complicated and scalable stack I’ve ever written.

Thanks to the complete web team, which apart from me is Cliffton 

So it goes like this.

• Our main backend app is written in Django (literally the superheroic web framework in Python),  usingMySQL as the primary database.
• The CMS and user facing frontend is written in HTML, using AngularJS (the awesome javascript framework written at google)  for structuring the frontend (using MVC architecture). For styling, we have used Foundation Framework (which we found better than Bootstrap) and SCSS for compiling style files.
• Our infrastructure is on AWS. We are using, at the moment, 1 EC2 instance, S3 for static and media files, RDS for MySQL. We are also using Redis Cloud’s managed Redis server for our Redis storage needs.
• Our primary web server is Nginx (which alongwith a web server, is also a reverse proxy server-eventually good for serving static files). However, we are serving all the static files from Amazon S3.
• Our chat is based on Django for logic and authentication, GCM for pushing messages to devices, NodeJS for websockets (for making chat real-time on browsers), local redis for pubsub (sending messages to nodejs to transmit to the browser) and managed redis for message storage and retrieval.

That’s just scratching the surface. I will for sure find time and post details for each component of the stack.

PS: Trying to get to a stage where things “just work”, and I can snooze for a while.