monolith | ⬛️ CLI tool for saving complete web pages

In Rails you can use "Shallow Nesting" which basically says to only nest the index, new and create actions under the parent resource. For the other actions you don't need to nest the routes, because through the record itself you have access to the associated record, so there is no need to have the id in the url.

So your routes will be:

I used a JDL similar to yours, without the enableSwaggerCodegen line and it works fine for me.

Make sure to update your Startup class to:

1. Add CORS services, and
2. Add CORS middleware.

As you already figured out, make sure to add the CORS middleware component before the call to app.UseHttpActivities() (which is the middleware handling HTTP workflow requests).

Sample code in ConfigureServices:

It's not really an error as it is logged at DEBUG level. Although it's confusing, you can ignore it.

It's a known issue that will be fixed in next release 7.1.0, see https://github.com/jhipster/generator-jhipster/issues/13835

The problem is with the JSON files in .Jhipster directory. Whenever we upgrade JHipster or import new entity, JHipster runs the entire entities using JSON files in .JHipster directory.

I couldn't get the exact solution but I did work around to get the solution. I just created new entity which is creating an issue. I imported the entity which generated new JSON file for the entity. I ignored other files created while importing this new JDL file. After this, I was able to upgrade the JHipster project.

You will have to define a ServiceEntry so Istio will be aware of your external service. That ServiceEntry can be used as a destination in a VirtualService. https://istio.io/latest/docs/reference/config/networking/virtual-service/#Destination

First of all, you need to check if it makes sense to have Product and Ingredient in a separated project. It seems they belong to the same domain.

Talking about a microservices approach you should not declare Ingredient entity as dependency of Product.

"APEX" is a set of stored procedures that is installed in the database. "ORDS" is a Java application that is installed on Tomcat and talks to APEX in the database. I wrote a guide on this a couple of years ago. Doesn't sound like you'd need the high availability or header authentication parts, but the initial setup is largely the same. It might add to your understanding, anyway. See here:

• https://pmdba.files.wordpress.com/2019/09/ha-oracle-ords-apex-with-http-header-authentication.pdf

I think you biggest bottleneck (it very well could be a code issue too but this may be low hanging fruit, and in general best to design for scale) is trying to run everything on the same server (Unless I'm not understanding correctly but that's what it sounds like

Everything is sat on a single contained node/nuxt application

With that assumption each of your applications should be placed on their own server so, as an example

Note: If you are not familiar with managing these services then I would probably look for a managed type solution

1. Redis server for caching X 1
2. Mongo server for DB X 1

DB and Redis are usually very performant so a single instance should be fine to start, not to say a cluster would not be needed but right now you should be ok

Now for the application stack you are going to want to break out each app to its own server, what this means is

1. Game (express)
2. Socket.IO
3. Rest API?

Should all be separate application, each capable of using the full CPU, without having to compete with other processes.

In you post you mentioned things started to slow down and lag, this could simply be the eventloop is backed up, Node ( single threaded ) will process in order of the request so if that keeps filling up, well things will take longer to process.

Now, you mentioned how you would do this, and well that is a big question and depending on who you ask you will get different answers, and the 'right' solution is going to depend on how much you want to manage and how comfortable you are with each technology. For example, you mentioned containers.. Containers are great! but if you are not familiar with Docker and Kuberneties and the concepts in general it can be a challenge and if you are a one man shop, well thats even more work..

So, as I'm sure cost is a factor because, well it always is but luckily its not too expensive to start..

Personally I use multiple servers and services from AWS, Linode and Digital Ocean (100.00 free credit), I like Digital Ocean (even though some dont, I have not had issues with them so I will talk in terms of using them)

Now getting started, you can always spin up multiple 'Droplets' and use PM2 to take full advantage of each CPU for each application, this works but you still need to add a load balancer etc, and to scale horizontally you need to provision new servers, configure and add them to the clusters, again this will work but its more work.

Digital Ocean does offer a service call 'Apps' that is basically a CAAS offering, that allows you to deploy from GIT to a container, letting you scale out horizontally very quickly, I use this service for my socket.io services.. When I know I'm going to have a heavy load, I just add a few more 'apps' to my socket server and scale from 2 to 6 servers in a few min, then when I'm not I scale it down..

So my TLDR is, break everything apart, you don't want to have apps competing for resources

*** Edit ***

Just to add to this, as @kissu mentioned, you can for sure use Heroku, very similar to DO Apps however (my personal experience here) they can be a bit more expensive but with auto scaling (DO Apps does not offer that). For me I know when I'll experience spikes so its easy for me to plan but with a game autoscaling may be something to look at or consider. In that case Heroku OR AWS may work better (AWS with Auto Scale groups with custom AMIs for your app)