feathers-vuex VS MERN-template

I deeply enjoy using feathers.js (https://feathersjs.com/) with Feathers-Vuex (https://vuex.feathersjs.com/). There's a CLI tool that gets you up and running fast: https://github.com/feathersjs/cli

Check out feathers.js, it generates rest routes for express and emits events on changes over websocket (socket.io), and even has a Vue library to manage sync

I am currently migrating to feathers with objection / knex in the backend and therefore switching to feathers-vuex So far I am pretty happy with the transition and the clean rewrite / service oriented structure from our "somehow grown" backend/frontend mess :-)

Feathers-Vuex ( https://github.com/feathersjs-ecosystem/feathers-vuex ) for anyone wondering, can highly recommend.

Anyway, the structure of this website uses microservices, driven by an engine I dubbed the MERN-template. It has it's own auth service, and supports both chat and a news feed. The game-specific elements are closed-source though (the idea is you fork the core repo, and build out from there).

i use mariadb, but yes.

Backstory: Decade Jam, a game jam that lasts for a decade, began Jan 1st, 2020. I started writing a web game called Egg Trainer, but after a year of work realized that my codebase wasn't workable anymore. So at the beginning of 2021, I began working on a game engine that would power the beta version of ET - this is called the MERN-template (clearly, I'm bad at naming things).

My MERN-template actually uses MySQL. There's no requirement that you do it one specific way.

I'd use the MERN-template project that I wrote myself. It's essentially the mern stack, except with MySQL.

I've basically written this thing from the ground up, including an open source engine that uses microservices.

Anyway here's my game engine.

Oh, I've done this with my MERN-template. It was designed to power my game, but I made it available for others to use.