What's your tech stack?

Nick Taylor (he/him) on April 25, 2018

Photo courtesy of Flickr user kreturn I came across this post from @ben today while I was doing some daily reading on dev.to. ... [Read Full]
markdown guide
 

Basics

  • git: Distributed version control system aimed at speed, data integrity, and support distributed, non-linear workflows.
  • gitflow: A git branching and release management strategy that helps developers keep track of features, hotfixes and releases in bigger software projects.

Languages

  • Ruby: A flexible scripting language with elegant syntax
  • EcmaScript 2015 / ES6: Current JavaScript standard.
  • SLIM: Template language whose goal is reduce the syntax to the essential parts without becoming cryptic.
  • SCSS: A scripting language that is interpreted into CSS
  • GraphQL: Powerful JSON like API.

Frontend

  • Vue.js 2
  • vue-class-components
  • Vuetify
  • vue-router
  • Vuex
  • Vuex-ORM A ORM for Vue
  • Vuex-ORM-Apollo Vuex-ORM plugin to sync against GraphQL API
  • Material Design Icons
  • Vee-Validate
  • jQuery: JavaScript toolbox for DOM traversal, event handling, animation and more
  • moment.js: Parse, validate, manipulate, and display dates in JavaScript
  • wow.js

Assets / Packaging

  • Webpack and Babel with Webpacker
  • Yarn

Backend

Persistence

Ops

  • GitLab CI/CD
  • Heroku: PaaS/CaaS solution
  • Amazon S3: Cloud storage solution
  • Rollbar: Error Notifications and Tracking

Testing

  • RSpec BDD Framework for Ruby
  • Capybara
  • Chrome Headless
  • Jest

Misc

 

There's tools like BuiltWith which are a good way to explore what other sites use. Although it can only use information that can be gleaned from the web responses, it can provide a surprising amount of insight into the stacks others use, especially on the front-end.

 
 

Siftery should also help as Stackshare tends to miss out on certain organizations.

The catch? On siftery, you can only view content on sign-up which needs a work email ID, i.e: Gmail / Hotmail / Yahoo won't work. A workaround I use is to create an account using email ID(s) via Temp-Mail

 

the only useful website i think is disposable mail its useful becaause its help you to reduce spam

 

Wappalizer Chrome extension is what I use. Been addicted to looking up other people's tech stack

 
 
 

Backend

  • PHP - Laravel
  • MySQL
  • Redis for Queues & metadata
  • Algolia

Frontend

  • Vue
  • React Native for Mobile
  • SASS

Deployments and Infrastructure

  • DigitalOcean (Droplet & Spaces)
  • Deployer
  • Nginx
 

Frontend:

  • next.js
  • React
  • Styled Components
  • PostCSS
  • Jest
  • Cypress

Mobile:

  • React Native

Backend:

  • Elixir
  • PostgreSQL
  • Elasticsearch

Infrastructure:

  • Heroku

Others:

  • GraphQL (half RESTful, kind of migration to GraphQL)

It's all open source as well here

 

Working at Fewlines, we're huge fan of functional programming and we build API-first softwares.

We use Elm for most of our front-end and we build the back-end with Elixir (OTP/Plug/Poison/Cowboy and sometimes Phoenix). PostgreSQL handle our data, RabbitMQ manage our events and ELK for logs related stuff.

Our server infrastructure is mostly "cloud agnostic" and based on Kubernetes (with Helm) & Docker.

 

Thank you for posting this! I know this is a few months old and I'm late to the party. Just want to say thanks for everyone to place more context outside of a simple builtwith query. We're dabbling in posting our tech stack and more in a dev blog. This thread is helping give more validation to posting a tech stack.

 
 

Primarily Microsoft .NET platform doing a little bit of everything from Windows services to WinForms to WPF to WCF to Web API to MVC (with some JQuery). Backends, mostly SQL Server and Oracle.

I've dabbled a bit in PHP, MySQL and Java but they have never been my primary focus.

 

Probably feels good to move over to Web API from WCF I imagine? 😉. Thanks for sharing.

 

It is, although I'm currently dealing with a mixture of legacy WCF and new Web API.

 

Front-end:

  • ES2018
  • Vue
  • Jest

Back-end:

  • Python (Flask and Django)
  • Ruby (Rails)
  • Go
  • PostgreSQL
  • Redis

Heroku, a bit of AWS (mostly S3 and Simple Notification Service), no Docker for now

 
 

Front-end:

  • React/Redux
  • Lodash

Back-end:

  • Rails

Deployments and infrastucture:

  • PostgreSQL
  • Redis (for Sidekiq and ActionCable)
  • Heroku
  • Github
  • CircleCI

I like to keep it simple.

 

Frontend:

  • LitHtml / React (Depend on the project)
  • Redux
  • Webpack 4
  • Webpack Dev Server
  • Babel 7
  • Sass
  • Polyfills
  • Es6
  • Npm scripts
  • Eslint / Typescript
  • Json Server and Fake Data
  • Yarn
  • Git

If I work with Angular I use their CLI and NGRX to handle the state.

 

I'm currently moving from a Java-based company to a Ruby one. So we can say my current stack is:

Backend:

  • Java 8 with Spring Framework (Spring Boot, Security, MVC, Data JPA)
  • PostgreSQL, Oracle Database, Microsoft SQL Server (depends on the project)

Frontend:

  • Angular 5
  • Vue

Our deployment method varies from project to project, the most interesting ones get to be deployed as Docker containers on our OpenShift Origin server.

At the new company they use:

Backend:

  • Ruby
  • Elixir
  • Some NodeJS if I understood correctly
  • Postgres
  • Redis

Frontend:

  • ReactJS
  • Some Vue
  • ERB for templating

Deployed on AWS ECS and some bare EC2 instances

 

Frontend:

  • React
  • Redux
  • Saga
  • Nodejs
  • Webpack

Mobile:

  • Native iOS (Swift and Kotlin)
  • Native Android (Java and Kotlin)

Back:

  • SpringBoot RESTful Microservices (Java and Kotlin)
  • MySql
  • MongoDB

CI/CD:

  • Jenkins pipelines

Infrastructure:

  • Docker Swarm + Docker Flow Proxy

Monitoring:

  • Prometheus + Grafana

Logging:

 

We have a few products, so the bird's eye view of our tech stack looks like this:

Backend

  • Python
  • DRF
  • PostgreSQL
  • Redis
  • MongoDB
  • Sentry (with sprinkles of Golang)

Frontend

  • ES6
  • AngularJS
  • React/Redux
  • Webpack (We are evaluating Vue for further projects)

Deployment

  • AWS
  • Docker/Docker Swarm
  • CircleCI
 

Just for variety, here are some of the tools we use for our desktop apps and analysis:

  • Matlab
  • Java (some GUIs in Swing, mostly CLIs though)
  • C\C++ (lots of boost)
  • Docker for building native projects, eventually for containerizing the app itself
  • Gradle (for Java and Native Projects)
  • AsciiDoc for documentation
  • Some CI in Jenkins
 

Front-End: RiotJS or VueJS
Back-End : ArangoDB + Foxx and Foxxy
Sometimes I use Ruby on Rails also but softly moving to 100% JS stack

Also moving to Crystal Lang when speed is needed.

 

Frontend:

  • React JS

  • ES6

  • Javascript (jQuery)

  • Yeoman/Gulp/Brunch

  • Recompose / Apollo

Backend:

  • Ruby on Rails

  • Elixir / Umbrella / OTP

  • PostgreSQL/Redis

  • GraphQL

  • Rest API

Infrastructure

  • Capistrano / Distillery

  • Heroku

  • AWS

  • Alibaba Cloud

  • Terraform / Packer

  • Docker / Kubernetes

  • CI/CD

 

Frontend:

  • Typescript
  • React
  • redux
  • Sass
  • Jquery (legacy scripts)
  • Smarty and PHP (legacy views)
  • Jest
  • Webpack

Backend

  • PHP
  • MySQL (percona)
  • In house framework - Garden (open source)
  • Memcached
  • Sphinx
 

Frontend:

JavaScript (VanillaJS, React, jQUery) - learning VueJS currently
ASP.NET MVC
npm scripts
PouchDB

Backend:
C# & ASP.NET Web API
Node
CouchDB
SQL Server
AWS & Heroku

 

Thanks for sharing Peter. Do you do SSR for React? I know there was some support for this with ASP.NET MVC a couple years back.

 
 

Front End:

  • TypeScript
  • Angular, React or Vue.js depends on the project
  • jQuery/ jQuery JavaScript
  • WebPack
  • Bootstrap or Material Design depends on the project

Back End:

  • ASP.NET Core/ASP.NET MVC C#
  • Node.js
  • Golang for writing APIs

Databases/Data Stores:

  • SQL Server, PostgreSQL or MYSQL depends on the project.
  • MongoDB, OrientDB or Azure CosmosDB depends on the project.

Tools and Editor:

  • Visual Studio Code
  • Visual Studio
  • Notepad++ for quick editing
 

My current stack:
Client-side:

  • Knockout.js
  • npm (build, test runner and dependency management)
  • Jasmine
  • LESS

Server-side:

  • .NET Core (C#)
  • SQL Server/MariaDb/SQLite

Hosting:

  • Microsoft Azure

My desired stack:
Client-side:

  • same

Server-side:

  • Go
  • MariaDb

Hosting:

  • Digital Ocean or Heroku
 
 

Front-end:

  • jQuery
  • Materialize CSS
  • SasS
  • NPM
  • Gulp
  • Apache
  • Amazon Linux

Back-end:

  • Python 3
  • Django Framework
  • MongoDB
  • Nginx
  • uWSGI
  • Gunicorn
  • Amazon Linux
  • PHP(legacy)
  • MySQL(legacy)
  • Apache(legacy)

All hosted by AWS

 

Frontend:

HTML5
Bootstrap

Mobile:

Swift
Objective-C
Flutter

Backend:

Elixir
Python/Django
PostgreSQL

Infrastructure:

AWS
Linode
DigitalOCean
Ubuntu

Others:

GraphQL
Neo4J

 

My current stack:
Client-side:

  • Knockout.js
  • npm (build, test runner and dependency management)
  • Jasmine
  • LESS

Server-side:

  • .NET Core (C#)
  • SQL Server/MariaDb/SQLite

Hosting:

  • Microsoft Azure

My desired stack:
Client-side:

  • same

Server-side:

  • Go
  • MariaDb

Hosting:

  • Digital Ocean or Heroku
 

Frontend:

  • jQuery
  • Bootstrap

Backend:

  • Python (Django/Twisted)
  • SQLite

Infrastructure:

  • Linode
 

Do you run your own Jenkins server or are you using Cloudbees? I'm curious to know what you're building too with a mix of Scala, Python and Node in the backend.

 

Not sure for Jenkins. I'll ask. For the other stuff, Node, Scala and Python for our Conversational Marketing Cloud Platform.

 

I was suspecting you did some AI stuff when I saw Python in the mix. But perhaps it's for something else. Looks cool!

No, you're right. It's for AI. Our platform uses AI.

 

Frontend:

1) Javascript
2) Jquery
3) AngularJs

Backend:

1) Php
2) NodeJs

 
 

Frontend: Angular, Razor with vanilla JS, Patiently waiting for Blazor
Backend: .Net Core, C#, PostgreSQL, looking forward to trying out CosmosDB

 

Heroku/Postgres/Rails/Webpacker/Bootstrap. About to add a new section with a different frontend, maybe Stimulus/Tailwind.

 

Frontend:

jQuery
Javascript

Backend:

Clojure
Postgres

Deployments:

Linode
git post-receive hook

 

Mine is:

Frontend:

  • Vanilla JS
  • VueJS

Backend:

  • PHP
    • PhalconPHP
    • Siler

  • Java

  • .NET core
    • ASP.NET core

  • Python
    • Flask

  • Ruby
    • Sinatra

  • PostgreSQL

  • Redis
 

Thanks for sharing Artemix. That reminds me. I forgot to add our databases.

 

Well I'm yet to apply for jobs, but I do work with Python Django, now Node.js and HTML, CSS, Vanilla

 

Mainly websites built with Drupal 7/8 - with gulp/yarn/sass - with MySQL backen. Cache is with memcached or Redis . Solr used for external search. Deployment done with drush and deployotron.

 

My stack lokks like This

Front-End

  • Bootstrap
  • Jquery
  • Ajax

Back-End

  • Python(Django)
  • Postgresql
  • Sqlite3

Deployement

  • Bitbucket
  • Obambu vps hosting
 

I work at a Startup and here's our tech stack:

Front-end

. React.js
. Bootstrap
. npm scripts
. ES6
. WordPress / PHP

Back-end

. Python
. Google Cloud
. Big Query
. NoSQL

 
 

Front end:
-Javascript
-React (Native for mobile)
-Vue
-SASS
-Webpack

Back end:
-Node
-Mongo db
-IBM Cloud

Infrastructure:
-Heroku
-IBM Cloud

 

Recently TypeScript for almost everything + Postgres for all database related things.

For work it is usually Python + MySQL.

 
code of conduct - report abuse