go-db | Generic database API for Go | Database library

• $match to match code condition
• $map to iterate loop of levels array
• $filter to iterate loop of modules array and filter modules that have code: "MC1_02"
• $mergeObjects to merge current object with updated modules field
• $filter above result if modules is not empty []

That's definitely an option. The thing to be aware of with an approach of microservices over HTTP is that then the endpoint is pretty much exposed to public traffic. If you use services like RabbitMQ or Redis, then there's no public facing endpoint that can be hit and has to be secured, only the API gateway to worry about.

But for your question: yes, that approach is fine and is probably the best way to go about it, unless you want to make a monorepo and keep them all in the same repo (I'd suggest Nx if that's the route you're going)

I have a feeling this is due to the mismatched driver versions. Version 3.9 has the method indicated in the error, but 4.2 does not.

Once you get that sorted out, you are going to want to change this line

You are combining await/async and Promise.then() syntax in a very confusing way. It is not an error to mix the two syntaxes, but I do not recommend it. Stick to just await/async

Your action actually does not return any value right now because your inner then function doesn't return anything. The only return is inside of the then is in the x.map callback. await syncItems is the returned value for the mapper, not for your function.

Right now, here's what your thunk does:

• open a connection
• get items from realm
• add a listener to those items which logs the changes
• returns a Promise which resolves to void

I believe what you want is this:

Could you try changing your referrer definition to:

$type is the operator you are looking for.

This is might be bad idea to do all process in a aggregation query, you could do this in your client side,

I have created a query which is lengthy may cause performance issues in huge data,

• $objectToArray convert months object to array
• $unwind deconstruct months array
• $unwind deconstruct transactions array and provide index field index
• $group by _id, year, month and index, and get first object from transactions in fields
• $project you can design your response if you want otherwise this is optional i have added in playground link

If I understand your issue correctly:

• You have secret with your password as environment variable, and pod has access to the secret data through a Volume
• You changed the secret password, but it's not getting picked up by a pod without a restart.

According to documentation:

Environment variables are not updated after a secret update, so if If a container already consumes a Secret in an environment variable, a Secret update will not be seen by the container unless it is restarted. There are third party solutions for triggering restarts when secrets change.

This is a known issue. You can read more about it in this github issue.

So after you change the secret password you have to restart your pod to update this value, you don't have to delete it.

As mentioned in documentation there are third party tools for triggering restart when secrets change, one of them is Reloader.

Reloader can watch changes in ConfigMap and Secret and do rolling upgrades on Pods with their associated DeploymentConfigs, Deployments, Daemonsets and Statefulsets.

The quick way to restart deployment would be to use kubectl rollout restart, which performs a step by step shutdown and restarts each container in your deployment or statefulset.

If you change the password in your secret and use kubectl rollout restart the new password should work.

First off, most of the questions are very opionated (at least the answers are) and your question will probably be closed for that reason. So I will post my answer before completing it and expand on it after.

First off a good roadmap to become a web developer. I like it mainly because it shows the crazyness the web development world has come to (don't be shocked!): https://levelup.gitconnected.com/the-2020-web-developer-roadmap-76503ddfb327

Trying to answer some of your question (answers are my opinion):

Is there some typical way to go / best practice while developing web-applications?

I'm tempted to say there are as many ways to do web development as there are web-developers in the world, but that might be a bit exaggerated. If you want some guidelines, I'd pick one of the major web frameworks and learn the way they do web development. With web frameworks I mean all kinds of frameworks starting with JS-frameworks all the way to static site generators, etc. They all have their ecosystem and their own rules.

What are the typical key players? I know there is the difference between front-end, back-end and databases.

(personal opinion) I work with Go in the backend. I love it because it brings back some simplicity in the crazy world of choices being a web developer. Since you know C, Go will probably be easy for you. It has static typing, structs, etc, but no need to manually manage your memory. It is also much faster than most other backend languages used in web development (Python, NodeJS, PHP, Ruby, etc).

In the front-end I have used native JS, jQuery, React, Vue, etc. I'm still waiting for something that makes things easy again. Flutter seems to be something that has a good approach, but is not really a web front framework (yet). (Don't do public websites with Flutter! They are not indexable.) We'll see where it goes.

Databases I will not go into here as that is another huge topic. Let's just say that I'm more a fan of using multiple databases for their specific strengths rather than a big one that is supposed to be good at anything.

which code is usually written in back-end / server-side languages?

Even this depends largely on your choices (framework and preference). One thing for sure has to be in the backend and that is security related stuff. Anything you put in frontend code is visible to an experienced user.

Apart from that there are some ecosystems where you don't write any backend code but talk to a (cloud) service that is basically like a database with a web endpoint on top with secured login. (for example https://firebase.google.com/.) Here the security related stuff is baked into the service.

If you do both, keeping business logic in the backend is probably a good idea. If the frontend calculates something (for quick response), the backend should double check that (e.g. calculating the total in a cart). But this is too general. There can always be use cases where some business logic needs to be implemented in the front-end.

Do I have to move all business logic into the back-end, also for security reasons or is this maybe also a bad idea because of performance reasons?

Performance can be a problem, but mostly because the roundtrip time to the server and back. If you do that for every tiny information, the UI will become sluggish. You might want to think about doing e.g. a calculation client-side.

JS-Frameworks like React, Vue don't request html from the backend, but data and build the html based on that data client-side. I'd use them if I have a very data driven website / webapp, especially if it is user-dependent. Transferring only the data and building the html for every site from it in the browser based on user settings and data, saves a lot of roundtrips.

If you are worried about server performance: For the server to hit its limit, you'd need heavy usage of your website for that to become an issue (at least with Go). If you get there you can still use horizontal scaling (multiple instances of you server) to solve that. Unless you are working for a large company with millions of users daily, I'd not worry about scaling for now.

What programming languages are more or less dead and not to be used in the future?

Warning: Very opionated!

I'd say PHP is dead. Many headhunters I've spoken with agree with me. Companies are desperately looking for PHP developers, because many developers are moving on from PHP to something "cooler". You'll definitely find a job with PHP, but might not be so happy with your job. For me it is also a sign of how modern a company really is (if PHP is not it's main backend language (any more)).

Python currently has a big boom. Mostly because of AI development. I'm not sure if that boom is also in the web development, but I'd say not. I used Python before Go (5+ years ago) and before that PHP (8+ years ago). I rarely get Python web developer job offers (at least compared to PHP and Go).

Go is the language of the cloud. It is perfect for concurrent programming which is an essential part in web development (every http call should be handled concurrently). It is fast and light weight and doesn't need anything installed on the server to run (compiles to a single binary without dependencies).

NodeJS: Haven't used. I'm not a fan of Javascript (but it was (and kind of still is) the only option in the browser), so I never liked the idea of using it also in the backend.

TypeScript: might be an alternative to JavaScript (thinking of frontend here) if you like a more structured language.

It sounded like you want to build a user baser web app with data being managed by each user. This is what I would (probably) do in that case:

• Backend in Go
• Go serves static files (start html, css, js, images, etc.)
• Go server has an api endpoint that serves data (e.g. REST style)
• Vue (or React) in the frontend
• Vue requests data from the api to build the user-specific content