What's your tech stack?

Xamarin Cross Platform Mobile Apps
.NET Core Web API backend
Azure CosmosDB data store

... mostly because these are the technologies I have experience in.

Managing a startup is not for the faint of heart. There's a lot going on and I need to know the team building my platform is "top shelf", on time, using superior technology, and willing to put up with our attention to detail, and our demand to develop the best product. That's why I decided to go with 8base.

I am building a web based CRM with 8base, and am happy with my decision. I like their ease of use, and dev team is local to my business.

Depends on what I am building, however, as my experience has been mainly Microsoft so I use C# to build my back-end (either Lambda or Functions) and Xamarin for front-end and mobile. I also use Angular usually for web. If the system uses alot of complex data structures I tend to use SQL Server but interact with it via the built-in JSON methods so it's like using a Dynamo / DocumentDB style database... or Oracle depending... otherwise I use DynamoDB or some other Document style DB. I tend to use serverless architecture and services in either AWS or Azure for pretty much everything I build now, especially in the early stages anyway.

.Net Core web app (MVC) with a postgres backend at CryptoTrader.Tax

I use Ruby on Rails for https://oneprofile.info

I've written about my tech and business stack here:
https://medium.com/one-profile/one-profiles-tech-stack-eec321f479f5

Hope it helps someone!

Frontend: Vue.js, Vuetify, Netlify, Firebase Cloud Messages
Backend: MongoDB Stitch, MongoDB Atlas, Netlify Functions, Firebase Cloud Messages
Other: Vue CLI, MongoDB Stitch CLI, Netlify Analytics

I wanted to reduce the amount of systems I have to manage manually - I think I achieved it with this stack.
Both Netlify and Stitch have automatic deployment from git, which means that I deploy both backend and frontend from my IDE with two clicks. At some point I was not happy with MongoDB Stitch, but with their latest updates, I feel like it was a good decision.

• What is your tech stack?
  Clojure, ClojureScript, React, Datomic, Google Cloud

• Your reasons for choosing them?
  Simplicity (https://www.infoq.com/presentations/Simple-Made-Easy/), Immutability (https://www.infoq.com/presentations/Value-Values/)

• And are you happy with your decision?
  Yes :-)

Javascript, NodeJS, RethinkDB, React, AWS

1. .NET Core for backend and desktop, TypeScript and Angular - for frontend

2. Have a long history working with .NET Framework (not Core) before. Now, with .NET Core, Microsoft takes a good speed of improvements and updates. The performance (especially for web-applications) has been increased significantly. And last but not least: I love the language (C#) and the tooling (Visual Studio, VS Code, etc)

3. Yes.

• Node.js, more specifically NestJS which uses Typescript
• Vue.js for front end
• PostgreSql as the database

And I host on Heroku or Google App Engine.

I use this stack because I'm productive with it and I can reuse a lot of code from older projects

My goal is to try out as many no-code tools as I can but so far Bubble, Webflow and Carrd all seem excellent.

MEAN...MongoDB, Express, Angular 8, Nodesjs.

I like opinionated, OOD, frameworks...easier to maintain, test, team manage, design and scale.
Yes, we can scale easily and rock solid.

Laravel + Vue on DigitalOcean with Laravel Forge to provision and manage the servers.

It's the closest I have to a silver bullet, and because it's own DigitalOcean I have cheap and predictable server costs.

Album Daily is written with:

Front End - React & Less
Middleware - Node.js Express app
Backend - Santiy.io headless CMS

These technologies were chosen on a mix of familiarity and need. React/Less/Node/Express I use at my day job, and Sanity was a perfect Headless CMS for our use case with a free tier (also recommended by the Syntax.fm podcast).

For https://tikker.co I chose what I know the best + decided to learn new front-end framework

1. Backend: PHP7, MySQL (I know them very well)
2. Front-end: VueJS (wanted to ride reactive hype a little :)) + es6 (wanted to get comfortable with imports, promises, spreads and all that stuff)
3. Hosting on Digital Ocean droplet /Ubuntu (I really like managing my servers)
4. DB backups on AWS (that's a no-brainer)
5. Mail sending - Amazon SES (for reliability and it's very cheap)

I considered dropping PHP and making the whole project on node.js, since there is not a lot of backend and it's a single-page app. But learning several new technologies at once seemed a bad idea: a lot of learning and not a lot of actually shipping.

VueJS turned out to be super cool, I'm very happy with it. Chose it having done some research here - http://todomvc.com/. In short - it's smaller, faster and more concise than React or Angular.

For Sitesauce I went with my usual stack (Laravel on the backend, Vue on the frontend and Tailwind CSS for sytling, and threw Inertia.js in the mix for connecting both frontend and backend.

React on the front-end and Node & MySQL on the back (built with Gravity). Hosted on Heroku.

It depends. WordPress for web store, Node JS for chat bot, Python for scraper, Unity for casual games.
And on my full-time job i was Java developer ;)

Elixir/Phoenix + Bootstrap. Vue.js components on certain pages if needed. Not sure about hosting yet, probably Gigalixir or Heroku.

Frontend : Vue.js, Bulma, Buefy, Axios, DreamHost hosted

Backend: Loopback, Postgres, MJML, Heroku

Currently Exploring : ElasticSearch, Message Queues (via Bull), DreamObjects (S3-like hosting by DreamHost)

----

This project started out as a learning experiment, so I tried FireBase and several NodeJS API frameworks (SailsJS, Nodal, Strapi, Feathers) before settling on LoopBack. It has so far met my needs, and allowed a good balance between auto-generated boilerplate endpoints, permissions, and custom functionality.)

I'm happy with my decision so far, seeing as how I tried several, hopefully my decision will scale when needed. Guess I just wish it hadn't taken me so long.

1. Frontend. Defenetly will pick Angular. I have started working with it from version 1.3 a long time ago and happy to stay with it.
   There are a lot of articles with comparing Angular with React, but for me I can determinate a few things that can help build and scale apps:

• advanced CLI
• the only way to build application architecture with official style guide
• a lot of components that works out of the box like lazy loading, routing, etc.

2. Backed. Express, Nestjs or Firebase based on initial requirements.

Netlify for the frontend hosting
Mongo Atlas for DB hosting in case on not Firebase set up
Digital Ocean for the server hosting