I am new to NodeJS development using NodeJS10.x version. I read questions and it turns out Javascript cannot be compiled, but I wanted to know if there is a way I can identify code issues before deploying it to production environment. I am developing a serverless application using serverless framework and deploying it on AWS. I use Aurora RDS with MySQL, so if there is a code issue the connection is not closed properly resulting in unwanted timeouts. And cloudwatch logs also doesn't show any error, so debugging is time consuming. Please advice with a standard way of handling such situations. Thanks.
Related
Good afternoon all, I have been running into a weird issue with the serverless cli tool over the last week. My team and I have an authorizer that we deploy separately from our APIs. When we deploy our APIs we attach said authorizer to the API gateway. All is good and well there. But our issue comes when we go to clean up a test API. When we run serverless remove on an API that uses the authorizer, the authorizer itself also seems to get removed, cloudformation stack and all. I am very confused as to why removing one of our APIs seems to remove a separately deployed authorizer. I was wondering if anyone could enlighten me as to a reason this may be happening, I don't believe I saw anything in the documentation if this is an intended feature or not.
We have been doing work on feature branches for our APIs and any time someone removes their test instance from our AWS account it also removed the authorizer. I have been under the impression that running serverless remove in a given project only removes the resources that the project itself spun up, not other things that it interfaces with as well.
Thanks in advance!
This was resolved, our naming we were using for both services was the same for some reason and so when one deployed it overwrote the other in cloudformation.
I was working on a project that needed a Database, and while I normally use MySQL, I decided to try MongoDB because I thought the schema/index model would be a better fit for what I was trying to do. Since then, I've used MongoDB in almost all of my Node.js programs. One thing that I found interesting about MongoDB itself was the hosting of it. I noticed that it was free, something that most commercial databases are not, and was intrigued.
After some research, I found out that when you create a DB, Mongo fires up a free AWS VPS.
I was wondering: Is this possible to replicate in Node.js? I would like to set up a VPS on AWS (free tier), connect a github node.js project, and run the Node.js project all from a remote project.
Could this be done?
Thanks :)
I have been planning to build a website through Node. But I really have no idea where to start. Upon my reasearch, I have seen various articles saying that I must try heroku in order for me to have a better understanding of node.
For my future development I want AWS to be my main server. The reason I'm asking this is so that if I begin my tutorial learning in heroku, I will be sure that it would be the same environment in AWS. Thanks in advance
I have build an chat application using nodejs with mysql database. I have developed on my windows system and it works fine.
Now I want to make it live on a server to check its real time performance, As a beginner I don't know which server hosting should I choose to develop nodejs application, so someone please suggest me a hosting for nodejs application?
If you want something relatively easy to test on, Heroku will provide you with a free instance.
I can also recommend Azure over Amazon for a simple nodejs based app. The main reason is that Azure has a very simplified interface for deploying node apps after a little bit of minor setup. Amazon offers similar capabilities, but the last time I looked at them they aren't quite as simple to get up and running. Again, they're competitive in cost and reliability, this is just a subjective opinion on what I think will be easier for a dev to get up and running without prior experience.
I use Dokku, an open source solution for a Heroku like PaaS. Either of those are great for doing git style deployments. Heroku has better documentation, and doesn't require your own server so I would start with them.
https://www.heroku.com
http://dokku.viewdocs.io/dokku
I have written a real-time multiplayer game and currently writing its server in NodeJS. I want my game to have login, level up etc, so I need to have a database. This is the first time I am deploying something and I am mostly self taught, so please correct me if I am mixing things up. Since this is my first trial, I do not want to make much commitment right away so I am looking for free options only. And since this should be a real-time game, I need a relatively fast server response. That is why I am looking for the easiest database and server provider that would do and I am aware that with those restrictions I have limited choices and functionality.
As far as I have read online, Heroku seems to be my simplest option for a server (that is why I started writing in NodeJS). However it seems like there is no free database service since all options on https://devcenter.heroku.com/articles/heroku-postgres-plans has monthly fee. I did not want to use Google App Engine since I am new (it certainly is not mentioned as beginner friendly).
So I have found AWS following Free Cloud Database Service for home development post, it seems like I could use Amazon Web Services as a server and database. However most posts I have encountered suggests Google App Engine or Heroku with little mention of AWS. Is this because I am mixing concepts up, or does AWS have drawbacks that I am not aware of? Do you think it is a good idea to use AWS for both as server and database, is it possible to use Heroku as server while using AWS as database or do you have any other suggestion?
Note: Sorry for the question bombardment but those are all related and I am sort of lost in this topic so I had to ask...
Use AWS EC2 for the server and RDS for the database. The reason why people use heroku is that it deploys to a custom url very quickly (it's easy to set up). Setting up AWS requires some knowledge of how servers work, but it's not that complicated (and it's free for small apps). Best of luck!