Just would like to find what every one else uses.
My Current Stack:
NodeJs (Epxress + Pug + Webpack)
For 95% of things my current stack is
Backend: Elixir/Phoenix, Postgres
Frontend: Bootstrap, occasionally react where needed, Apollo when doing graphql stuff.
I'm thinking of using Phoenix as well, can you tell me if you can create just a JSON API to hook into react instead of using Phoenix for server side pages, and if so, how?
Phoenix is great for making JSON APIs.
Unlike Rails or Django, the overhead is minimal vs just using Plug/Sinatra/Flask, so there's little reason to jettison it.
You run alchemist.camp! I've been using your videos to learn Elixir, great stuff, thanks! Do you have any about using Phoenix to create just an API without all the frontend templating and whatnot? I'm looking to use it for Vue.
Thank you for your kind words!
No, I don't, but I'm planning a short series on the topic. A couple of others have emailed this exact request.
Craft CMS (headless if needed)
I’m more of a serverless guy myself.
The stack for https://appreviewbot.com is:
React for the frontend
Hosted on S3
Cloudfront for CDN
API Gateway and AWS lambda for the API
DynamoDB for data storage
Lambdas power the review collection
Cloudwatch for monitoring/alerting
I am particularly fond of this stack since you can get really far without having to pay anything.
My stacks either are:
Clojure + Clojurescript + PostgreSQL. I really like Luminus.
Elixir + React + PostgreSQL. Phoenix channels are really cool.
I usually build my stuff using Postgres with either elixir + phoenix or ruby + rails, but I really want to stay away from react/angular/whatever-js on the frontend.
I've been experimenting with a full clojure app on the frontend and backend and I'm enjoying it. It's good to be able to use one language for everything, but it's going to take a while to get used to it.
My default stack is:
TailwindCSS or Bootstrap
Soon to be Phoenix LiveView
Interesting to see Elixir and Clojure get a lot of interest here, I would've expected all JS with Node and React.
Rails, mongodb, stimulusjs and bootstrap.
ArangoDB, CockroachDB (depends on app)
Angular/React (depends on app)
Very similar to @shawn_maplegum, for just about any web-based projects I use the following:
Elixir/Phoenix, Postgres, Absinthe if I need GraphQL.
I sometimes use Rails for some more traditional projects or quick throwaway MVPs, but I'll probably never voluntarily choose Node again.
Preferably just Turbolinks/Stimulus JS or Vue in specific pages.
If it's really a full-blown web app, I'll use React+Apollo.
Bootstrap SCSS is still the quickest and easiest for a quick project, but I've been playing around bit with Vue Element and with Material Design.
Interesting to see you use Vue for one off pages and react for full apps. I've not spent much time at all with Vue to be honest but I would have thought the opposite would be more common. Is it really easy to use in a component or one off page use case then? Might have another look if so.
To me Vue now feels like React did in 2014. It's easier and faster to get started, it's gaining steam quickly, has a ton of github stars but isn't so big in terms of professional use (outside China, at least). React's usage leans more towards the enterprisey side in 2018, just like Angular of 2014.
Vue is about as easy to drop into a project as jQuery. What really opened my eyes in terms of its use with back-end MVCs was what the Laravel community was doing with it.
Thanks for that perspective.
I am new to Vue and have not instrumented React or Angular either.
But I find Vue easier to learn and implement. Haven't had a chance to do server-side rendering yet but its next in the list.
I will explore React & Angular to see how they compare.
Thanks for that info. I noticed one of the designers I work with had a bunch of vue repos on their github profile today. I'll give it another look.
Rails, Postgres, Redis, Hatchbox on DigitalOcean, and Bootstrap. Looking into Spectre.css as well as it's soooo much lighter than Bootstrap.
Depends on the project, but I have a couple:
Firebase / React
Heroku / PostgreSQL / Rails / React
For Styling, lately I have been using Bulma / TailwindCSS and trying to get away from Bootstrap as much as possible.
On mobile, I use Flutter.
I'm a user of Bulma and was thinking of taking a look at Boostrap, just to see why it's so much used. So, out of curiosity, why do you try to get away from it ?
Basically, most people throw it on there including all the plugins/etc. It's a huge amount of CSS / JS and most sites don't need all of it.
Yeah, but it speeds up the development process quite a bit once you get used to it. I don't find that extra css/js to be that much overhead and it does not impact the overall experience (let's be honest, we're talking about a few hundreds kb at most)
Yes and no. I don't find any of the JS useful as I'm all React now, and the built-in stuff just isn't great. The CSS is fine, but even a lot of it isn't useful, compared to say, Bulma. It was great 4 years ago, but now it's just bloat.
Currently still in the prototyping phase, so right now it's Foundation and JQuery on the frontend, which is accessible to me as a designer. We'll be building with Rails/Postgres/Puma/Nginx, according to my full stack partner. Overall, we're trying to keep things as simple and maintainable as possible, leveraging our current skills.
I've been reading a bit about Stimulus, and will try some experiments with it to see if it has a place in the project.
Ruby On Rails
Bootstrap + Material Design
Clojure, ClojureScript, Postgres, Heroku, Bootstrap.
That's what powers https://trolley.link (and any other ideas I've come up with in the last few years)
Dirty PoC: (small functionality I do not think I will iterate)
Backend: PHP + json files
PoC: (I think I will iterate)
Backend: PHP + [Mysql] (sometimes JSON files for first versions) + [slim] + [rest api] (if Frontend has react)
Frontend: Bootstrap + [react] (if I think I will need to iterate many times)
PHP as backend because I am comfortable with it and deployments are a matter of a ftp or rsync command.
Lately I am playing with firebase or any other similar solution as backend instead of PHP + JSON files for PoC. I do not have any conclusion yet. But probably I will blog about it.
I am not really with any of the backend frameworks I have used. Laravel is so huge for my usual needs. Lumen falls short easily and you end up needeing to update to Laravel. Slim is what I recently use, but meh...
For every idea I come up with, I use
Django, whichever is the latest version
Templates From Bootstrap
Launch it on Heroku
Static Files on AWS S3
Database: MySQL 5.7
Front JS: Vanilla
Front CSS: Bootstrap
I love Laravel, so for most of my projectd my stack looks like this
Laravel 5.6 or 5.7
It's the same stack used in my latest project : https://laravelcollections.com
As a guy who does feel completely overwhelm by all this JS frontend choices, and not very comfortable with so many options I try to keep it simple:
Ruby on Rails (5)
VPS with Ubuntu Server
My project is not extremely technical (tourist and business information and consultation) but I get to earn some money.
Node with React, Bootstrap, Express, and MongoDB.
Unnamed Product (a Mac application):
Website (https://nottoobadsoftware.com/, just a blog at the moment, landing page coming soon):
plain HTML and CSS
repository on GitHub (https://github.com/kareman/nottoobadsoftware.com)
built on Travis
Hosted on AWS S3
AWS Lambda, APIGW, DynamoDB, Cognito, SNS, SQS
I can do multiple stacks, but so far mostly use Rails + PG.
I don't have much preferences in front-end stacks, but i avoid react/vue as a plague. I tend to lean to somethings simpler -- turbolinks/stimulus and/or riotjs.
I also didn't found my perfect css stack -- so far i'm experimenting with bulma and tailwindcss on my main projects.
Most of the projects I host on heroku. CircleCI has a very generous free tier that I abuse to get static code analytics and to run automated test on every pull request in github.
Python is my go-to language.
Django is my web framework of choice. Sometimes I'll use Flask for a quick prototype. Sometimes even Jekyll for non-database projects.
Django Rest Framework is my goto Rest/API framework
Postgres is my database of choice
Tailwind CSS is my goto CSS framework
Digital Ocean serves my projects
Github for public projects
Gitlab for private projects (better account and CI options)
Django (particularly DRF)
I also find that you can run the above stack using docker compose with amazon EC2 and RDS and stay mostly within the free tier
Firebase + node
can cost pennies if you know what you're doing and super simple to start.
Whatever solves the problem well and is easily maintainable.
AWS Lambda, API Gateway, Dynamo/Aurora, etc.
Front: Bulma / VueJs when needed
back-end: AdonisJs (real time saver, I wrote about that https://hackernoon.com/my-takeaways-from-building-a-job-board-with-adonisjs-4-f4071d98a929)
This comment has been voted down. Click to show.
It's that your actual go to stack? Some of those things don't really make sense for the question?
That is my stack
Right but like blue-green pattern is a deployment strategy not part of a tech stack.
Multi-tenancy again is a technique not part of a tech stack.
"scale postgres multi-node with catalog db" what is catalog db? I've used postgres for over a decade and I've never heard of it and a google search turns up nothing?
DBaaS is how you host your database but again not really anything to do with a chosen stack.
Your go to stack for a new project includes consul, app server clusters, and multi-node postgres? That seems overly complicated. The whole thing seems a bit like keyword bingo.
It's not too complicated to understand it's too complicated to be real. I've architected and built some very large high traffic advertising platforms before. I know scaling. I also know when someone is making stuff up trying to sound cool. If you do honestly use half this stuff as your go to stack you're a bad engineer and need to take some time off technical blogs from FAANG companies.
Blue green deployment strategies don't replace dev servers at all. They are about reducing downtime and detecting faults in deployments nothing to do with dev servers.
Great could you link to the paper? About "postgres multi-node with catalog db"? I'd love to read it.
I don't see anything about catalog db there?
Anyhow I agree this is just getting embarrassing to read.
If lying about this makes you feel better though you need to reevaluate your priorities.
Again you attack me.
Quote from azure
"Sharding adds complexity both to the design and operational management. A catalog is required in which to maintain the mapping between tenants and databases."
The catalog db is in my environment, while the multiple postgres db nodes are a DBaaS so they continue to scale limitless.
My market serves 109 million users. And i want a system that does not require re engineering as i grow.
As i said this is my go to stack, operational and error free.
We have built 4 SaaS products all live and growing.
This comment was deleted 3 months ago.