1

Topic: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

There is a web application (not highload) which now works and  in IIS. From IIS rise on the first request and restarting if fell (WAS) is used only. There are thoughts to pass on , however there are fears that world experience rejects such approach. Who has such experience and whether it is positive?

2

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

There is a web application (not highload) which now works and  in IIS. From IIS rise on the first request and restarting if fell (WAS) is used only. There are thoughts to pass on , however there are fears that world experience rejects such approach. Who has such experience and whether it is positive?

It is positive. But anyway, the Web server which sticks out outside is necessary. It can be IIS, nginx or other Web server, which  requests in service. Outside  it is impossible to let out.

3

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

hVostt wrote:

Outside  it is impossible to let out.

why?

4

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18;
I against)).
There is a Web application in the intranet of a network and is Win servis, e.g. SOAP.
If at you upon, instead of on a title a web the project a lot of the tasty weather-cloth will be on IIS.
For example, adjacent a web application, or was recently about enterprise roles.
It is scalability.

5

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

hVostt wrote:

It is positive. But anyway, the Web server which sticks out outside is necessary. It can be IIS, nginx or other Web server, which  requests in service. Outside  it is impossible to let out.

And we think, iis to leave as  and a reverse-proxy with  SSL.
You could not impart experience more in detail?
Interests as you implement balancing and how you implement life cycle of servers?
For example it is necessary to update the version, you stop service, copy new bins, then launch service?
Whether there is at you a similarity of web gardens for fail safety?

6

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

Petro123 wrote:

void18;
I against)).
There is a Web application in the intranet of a network and is Win servis, e.g. SOAP.
If at you upon, instead of on a title a web the project a lot of the tasty weather-cloth will be on IIS.
For example, adjacent a web application, or was recently about enterprise roles.
It is scalability.

Upon at us very big  application, in plans - migration on.NET Core but while only it is divided it into microservices, we want to receive experience of development of microservices, but without IIS. Are ready to sacrifice functionality IIS.

7

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

it is passed...
And we think, iis to leave as  and a reverse-proxy with  SSL.
You could not impart experience more in detail?
Interests as you implement balancing and how you implement life cycle of servers?
For example it is necessary to update the version, you stop service, copy new bins, then launch service?
Whether there is at you a similarity of web gardens for fail safety?

At us the main application is twisted on 7 servers in so-called Auto Scaling Group (Farm).
For loading equalization answers HAProxy, from IIS ARR refused.
If it is necessary to update the version it gathers, baked a new image of the machine.
Any amount of machines rises (2 for example), on them the part of clients is started up.
We are convinced that all is good. We lift still machines, we start up there still clients.
And so gradually all move to the new version, and old machines are extinguished.
This technics is called Canary Release .
Is still Blue-Green Deployment, there under the link see.

8

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

it is passed...
Upon at us very big  application, in plans - migration on.NET Core but while only it is divided it into microservices, we want to receive experience of development of microservices, but without IIS. Are ready to sacrifice functionality IIS.

Full articles of type of this: https://www.3pillarglobal.com/insights/ … ore-docker

9

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

in plans - migration on.NET Core,

It I support, as mastering of new trend MS.
Microservices I do not support.
Here such dilemma.
The criticism of microservices is a separate subject. It is that in java that in  that in a network.

10

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18;
IMHO a subject in a century integrated circuit Development I think too it will be useful. There the spectrum of judgements and technologies is wider.
Or at you only  around?

11

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

Petro123 wrote:

void18;
IMHO a subject in a century integrated circuit Development I think too it will be useful. There the spectrum of judgements and technologies is wider.
Or at you only  around?

At us only , all office on it writes. Docker unfortunately we can not, since it is necessary to support second-hand articles  Win2008R2/2012R2.

12

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

skyANA wrote:

it is passed...
At us the main application is twisted on 7 servers in so-called Auto Scaling Group (Farm).
For loading equalization answers HAProxy, from IIS ARR refused.
If it is necessary to update the version it gathers, baked a new image of the machine.
Any amount of machines rises (2 for example), on them the part of clients is started up.
We are convinced that all is good. We lift still machines, we start up there still clients.
And so gradually all move to the new version, and old machines are extinguished.
This technics is called Canary Release .
Is still Blue-Green Deployment, there under the link see.

And how you roll migrations on a DB?
At the moment of update put  on record in a DB and update the DB circuit?

13

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

it is passed...
And how you roll migrations on a DB?
At the moment of update put  on record in a DB and update the DB circuit?

any , we support two versions during time

14

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

skyANA wrote:

it is passed...
Any , we support two versions during time

. At you NoSQL?
Question then how to synchronize the given DB of the old version which have been written down during the moment  in the new version of a DB?

15

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

skyANA wrote:

it is passed...
I.e. you  in AWS?

16

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18;
You read about Canary Release?

17

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

it is passed...
Yes, last year moved there.
But also before the circuit was about same. Handwork only was more.

18

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

And it is thought, iis to leave as  and a reverse-proxy with  SSL.
You could not impart experience more in detail?
Interests as you implement balancing and how you implement life cycle of servers?
For example it is necessary to update the version, you stop service, copy new bins, then launch service?
Whether there is at you a similarity of web gardens for fail safety?

At us nginx as a Web server.
Web applications on asp.net core are published in a type of services and dockers-containers.
Completely 100 % all  on Octopus, server groups for seamless release are divided on tenants, packets with releases are allocated local nuget repositories, in the same place units for the assembly.
When it is necessary to update the version, we come in Octopus, we push, Create release, the channel of delivery and we press button Deploy. When half of machines , turnes on the mechanism of transfer of users on new machines when they are thrown, all connections are closed, the trigger and either in manual, or in an automatic mode is launched, happens  on a remaining half.
There are mechanisms  as all at once, the full automatic machine. And it is partially possible  subsystems, services, services separately. All seamlessly.

19

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

At us only , all office on it writes. Docker unfortunately we can not, since it is necessary to support second-hand articles  Win2008R2/2012R2.

You can use Octopus Deploy.

20

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18;
In containers it is offered to wrap new microservices, instead of second-hand articles.
The so-called technics of suffocation:-Q

21

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

hVostt;
Did not understand what method of a DB changes?

22

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

hVostt;
Example:
The address was in the line, became essence. I.e. a minus a field and plus the table.

23

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

Hm. At you NoSQL?
Question then how to synchronize the given DB of the old version which have been written down during the moment  in the new version of a DB?

The basis is twisted on MS a SQL Server. But is and MongoDB, Couchbase, ElasticSearch, Postgres.
The circuit of the main DB changes rarely but as the new version at first is rolled out to a small amount of users always it is necessary to think of how it to support.
Frequently it dares triggers.
Migration happens in two stages: before  the new code and after all users passed to the new version.

24

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

void18 wrote:

the Question then how to synchronize the given DB of the old version which have been written down during the moment  in the new version of a DB?

I join a question.
Itself I know such methods:
1. EF magic
2. Scripts on   and a post of AppAdministrator
3.  the internal mechanism allowing some versions .
Whether I do not know the sequel is able.
4. Replication

25

Re: Self-hosting ASP.NET Web API applications in a Windows service? Somebody used the such?

As as. To write and to an old place where the address was in the line and in the new table.
When all move on the new version to beat an old place.

Posts [ 1 to 25 of 50 ]

Pages 1 2 Next

You must login or register to post a reply



Random topics