How do I migrate a web service endpoint to new system without having to recreate it from scratch on the new system? Basically move it from dev to production.
You can create a customization package where you can added your web service endpoints and publish it in production.
Related
I'm new to AWS environment. I've few questions regarding AWS deployment. An important point to remember here is that I am using free tier of AWS. So I've limitations about resources.
Question1:
I've developed a web app on my local server (using VM with centos Linux) which uses React-SSR for the frontend using Express server. React CSR and SSR is generated using webpack. Backend uses Django as main framework, postgreSQL for database. Frontend and backend communicate with the help of Django Rest Framework. Gunicorn is used to run backend server. I want to use Nginx as reverse proxy server. How can I deploy this app on AWS Elastic Beanstalk? Can Amazon S3 be used to run React-SSR frontend?
Question 2:
This app serves images which'll be uploaded through backend. What's the proper way to handle images and static files with this kind of app? Should images be handled by nginx, react or django? How should I configure Django so that it stores image paths properly in its model(ImageField is used)? Where does Amazon S3 fit in this?
Question 3:
Can this app be made region agnostic under free tier?
The answer to the first question: React can be deployed on AWS S3, if you configure webpack for generate static files (HTML + CSS + JS), or use the NextJS for generate static on build.
The answer to the second question: To use AWS S3 for storing statiс use django-storages
We're developing our web app on google cloud and we are using firebase as a database and auth functions. Can we deploy our app on AWS or Azure? Is it a problem using firebase?
This is too broad question , but generally speaking if your app uses firebase and you deploy on AWS or Azure it works there is no problem due to firebase being a database.
Thanks
My question if is it possible to discover or integrate axis2 web services with WSO2 Governance Registry?
I want to discover all the web services and automatically upload their info to the WSO2 GREG, and check automatically if there is a new web services.
Yes you can do this with WSO2 Greg and Application server. Here are the steps you required.
In jenkins(or any other task scheduler to check available services frequentrly) we will deployed scheduled task to trigger some event periodically.
Periodic task will call WSO2 App Server’s admin services to get service metadata. To list service meta data for axis2 services we can call service admin soap service (https://127.0.0.1:9443/services/ServiceAdmin?wsdl)
In same way we can call all services and get complete service data(if you need other service types in addition to axis2 services).
Then we can call registry rest API and push that information.
Please refer this article for more information about Registry REST API.
You can find detailed description and soap service details in this article.
Am new to Amazon Cloud service, I have to create a web application using Springs, Maven and Amazon DynamoDB. For that I have to create in Amazon Elastic Bean Services only or normally we can create a Maven spring project and include amazon dynamodb dependencies and deploy to Amazon EC2 cloud service. Now I really stuck with it? .. How to create a web app with Amazon enabled services?
Try to use jcabi-dynamo, a simple object layer on top of Amazon SDK. For your Maven project I'd recommend to use jcabi-dynamodb-maven-plugin, which will help you to automate integration testing of your DynamoDB-empowered application.
I have created a "Windows Azure Cloud Service" project in VS2012.2 with a MVC4 web role. When I run up the project it just gives me a web page. I am trying to develop a web service back-end for my website so I want to be able to call web methods directly from my website which is also running in on Azure.
When F5 my project it just gives me a website. Should I be using a worker role instead of a web role?
If you put your back-end web service along with your web role, then you can use it directly.
If you put your service in a worker role, then you need to open an input endpoint on your worker role so that it can be connected from out side of azure.
Or, you can create another website for your service and map to a virtual dictionary/application on your web role.
You may use both, but a web role is easiest as it sets up everything for you.
Its better to use web role in your scenario, the reason being publishing a web role is pretty straight forward.