What's your tech stack?

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

• Ruby on Rails 5 Ruby standard web framework.
• Trailblazer 2 High-level architecture for Rails. We use Cells, Operations, ROAR
• AuthLogic Lightweight authentication solution for Rails
• Pundit Authorization library
• ActiveAdmin: Ruby on Rails administration framework

Persistence

• PostgreSQL: Most advanced open source DBMS

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

• Google Analytics: User Tracking
• UserReport: User Feedback

Backend

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

Frontend

• Vue
• React Native for Mobile
• SASS

Deployments and Infrastructure

• DigitalOcean (Droplet & Spaces)
• Deployer
• Nginx

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.

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

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.

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.

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.

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
• 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:

• Logz.io

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

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

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.

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

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.

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