Ask HN: What tech stack would you choose for a serious, long-term business app • Hacker News Board

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#21

Post by bauerd » Thu, Apr 05, 2018, 1:20 PM UTC

nathan_f77 wrote: post #10

DB: Postgres API: Ruby on Rails Frontend: React, the react_on_rails gem to set up webpack, Flow, Redux, Immutable.js Background Jobs: Sidekiq and Redis Caching: Memcached PaaS: convox (on AWS). See: https://convox.com and https://github.com/convox/rack (But you should start with Heroku.) I recommend the Rails stack. It's not the "hot new thing", but it's very stable, secure, and productive.

My favorite stack as well, minus Convox (haven't heard of it before though). A no-brainer for me personally, unless there are realtime requirements.

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#22

Post by Gonzih » Thu, Apr 05, 2018, 1:21 PM UTC

Postgres + Go + Vue.js + Redis + AWS

Go with or without any framework (like Buffalo)

Vuejs with Vuex

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#23

Post by jpetitcolas » Thu, Apr 05, 2018, 1:22 PM UTC

Your technical stack should not be frozen. During years, it will probably evolve, either to use some promising features of new technologies, or to still be able to hire. For instance, hiring some Cobol developers is really hard (and then expensive) these days.

More important than technologies is testing. If your whole app is well tested (with both unit and E2E tests), you won't be reluctant to upgrade some part of your system because it doesn't answer your needs. Moreover, it would bring a lot of reliability and would be self-documented. That's the biggest point IMO.

For nowadays mood, we are really glad using React, Node, GraphQL and PostGreSQL for all our apps.

Note: we wrote a blog post about one of our long running customer story, which may interest you: https://marmelab.com/blog/2018/03/28/1859.html

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#24

Post by NursingEssays » Thu, Apr 05, 2018, 1:22 PM UTC

Such a best things you said in this topic.....

http://www.ukessaypapers.co.uk/

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#25

Post by petraeus » Thu, Apr 05, 2018, 1:23 PM UTC

Ruby with rails or php with laravel, the js stacks are too new and too hip for a long term application, go with a mature stack that doesn't change with the wind

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#26

Post by chronid » Thu, Apr 05, 2018, 1:23 PM UTC

I'm not sure about the stack (depends on what you are comfortable with, your requirements...) but:

1. use something that has been around a long time and is well supported/known

2. you probably don't need stuff like cassandra or other "big data" data stores (just yet). PostgreSQL/MySQL is plenty fine to start with (and easier to manage/think about).

3. please use only a single cloud provider.

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#27

Post by wasted_intel » Thu, Apr 05, 2018, 1:23 PM UTC

happywolf wrote: post #13

Is your business just starting, or already have some customers? How much funding you have, and what are the skillsets of your staff have? A safe place to start would be Linux + Postgres + Java Spring or PHP Laravel. My experience is the market has more Java or PHP engineers (compared to say, Elixir).

> the market has more Java or PHP engineers

That's a quantity over quality argument. Assuming there isn't an extreme shortage, I'd opt for a language and/or framework that tends to attract higher quality candidates. Personally, Ruby/Rails feels like it hits the sweet spot there.

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#28

Post by nielsv » Thu, Apr 05, 2018, 1:23 PM UTC

For our SAAS we're running:

- DB Engine: MariaDB on RDS (multiple instances) + Redis for specific use cases. - API layer: Symfony (PHP) - Frontend : React - Caching: Redis - Ops: Rancher Orchestration on EC2, and a bunch of AWS features like S3, ALB, ...

We had some hiccups here and there, but I'd say we are happy with the stability of it.

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#29

Post by Tobani » Thu, Apr 05, 2018, 1:24 PM UTC

setquk wrote: post #12

nathan_f77 wrote: post #10

DB: Postgres API: Ruby on Rails Frontend: React, the react_on_rails gem to set up webpack, Flow, Redux, Immutable.js Background Jobs: Sidekiq and Redis Caching: Memcached PaaS: convox (on AWS). See: https://convox.com and https://github.com/convox/rack (But you should start with Heroku.) I recommend the Rails stack. It's not the "hot new thing", but it's very stable, secure, and productive.

Definitely agree with memcached. This has been entirely bullet proof for us for years. We have had lots of nodes with billions of hits each running non stop for 3 years without a reboot on CentOS 5. Zero maintenance required. Amazing bit of software.

While memcached is great. I feel like its hard to argue for both redis AND memcached. It seems like redundant infrastructure unless you have very specific needs.

Re: Ask HN: What tech stack would you choose for a serious, long-term business app

#30

Post by unclebucknasty » Thu, Apr 05, 2018, 1:24 PM UTC

setquk wrote: post #6

As we're talking business and long lifetime... First point: nothing Microsoft. Done that show for 20 years and been through all the marketoid schizophrenia promoted rewrites for no business value. Now the new "start again" is .Net core and a big chunk of stuff just isn't portable and never will be. Plus the price gouging, licensing hell etc when you have to scale up. Entire ecosystem is a wasteland of unmaintained cr…

Wow, that's pretty hardcore...borderline badass!

Interesting thing is this stack was doable probably 13+ years ago, so I see your emphasis on stability.

Anyway, it's similar to what I'm using and surprised to see it here. Biggest tweaks are that I'd consider Vue/Webpack if starting today and do believe PaaS to be far superior to on-prem/colo. Also, not big on Hibernate or too much abstraction at the data access layer.