i have to deploy my mern application which is small scale student entry application. I am using mongodb atlas as db so which one will be cost effective deployment and please suggest a platform
I have no idea regarding deployment and am doing it first time
Related
I'm working on a Node.js project on Cloud Foundry and BTP using PostgreSQL as the database, now when I need to change a table structure I made changes in the data-model.cds and redeploy the project in the BTP space, what I want to develop is a database migration manager that can handle and run migrations and make changes automatically without removing the PostgreSQL instance and redeploying my project.
I didn't find a technical way to start doing that and there is no documentation that can help with PostgreSQL database.
Can anyone help ?
I am beginner in elastic search.I have implemented elastic search for single node with NEST Client in my C# Web Application successfully.Now I want to scale my data horizontally and want to deploy this application on Azure cloud storage.so if any article or documentation(step by step) is available for how to effectively deploy Elasticsearch with proper configuration on Azure with multi node then inform me.
Any suggestion is appreciated.
Take a look at Elastic's Azure Marketplace offering. Within a few screens and minutes, you'll have a cluster deployed on Azure.
If you need more control over the deployed cluster such as
number and size of disks to attach to each data node
install Azure repository plugin for snapshot/restore
Java heap size for each node
take a look at the ARM template on GitHub. This is the same underlying template that powers the Marketplace offering, but deploying directly provides more features than are exposed in the Marketplace UI.
I have a web app in ASP.NET Core RC1 in production and deployed in Azure with thousand of users using day a day.
I'm now upgrading my web project to RC2, following the tutorials I have found on Google (for example: Scott Blog, Official Doc, Tutorial1, Tutorial2, Tutorial3)
I need deploy the version RC2 when I have finished the upgrade without lose service to my users.
Do I need to create a new web app for the RC2 version or can I deploy in the same web app?
What is the way to implement that?
Thanks.
You can use Azure Deployment Slots. Develop and test your web application on you local, push it into the Staging slot. If it works fine there just swap the Staging Slot with the Production Slot. If the test fails there, don't worry, your actual application will still be running in production. Swap them carefully.
If you are using a storage with your web app, create a test (if possible) database in Azure for Staging Slot. If database is not an issue, you can use the same database with Staging and Production. Make sure that it works fine on your local system first.
I'm proposing my company start using Azure Web Apps for our Web App. Others would like to set up Azure Virtual Machines to run the web app, only the web app.
The reason they would like to do that is because of the way they currently handle roll outs. I would like to find documentation on how this is handled with Azure Web Apps.
Currently we have 2 servers that are load balanced. When it's time for a deployment, we bring down one server, updated it, then switch to that server, bringing down the 2nd server to update that.
I'm sure there's a better way to do that using Web Apps. I'm not completely familiar with the server end yet, but am trying to get information.
What we want to avoid is the user getting 30-60 seconds of load time if we publish a change.
Web Apps provide multiple deployment slots, specifically to allow for multiple deployed versions (e.g. production, dev, test).
Also built-in is the ability to swap slots. This allows you to deploy a new build to a testing slot, test it, then swap with the production slot. At that point, your end users start working with the new app version. Your previous version is in the other slot (until you tear it down).
More information on Web App deployment slots here.
I've a MVC Web Application (.NET) and from time to time I need to upgrade the deployment version on Azure, the problem is that I have customers that are using the Web-App and I cant take it down and make it unavailable.
There is a way to deploy a new version of my Web-App and still be up and running the all time? (during the deployment process)
One way that I could think of it to do it is by deploy the the Web-App to somewhere other than my current deployment and "play" with the DNS record on my external domain.
Use deployment slots.
Azure Web Apps let you create staging slots for your site. They're effectively independent sites that you can deploy your test/staging bits to.
Then when you have the staging site ready you can push a button and make it your public production site.
See here for more details: https://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/