Testing out AWS lambda EC2 Managed Instances with our AppSync GraphQL API to see if cold starts really go away.
To build your Asp.NET Core 1.0 application in Appveyor, a bit of configuration is required to tell the Appveyor build agent to get the dotnet core compiler. The configuration steps will install the .Net Version Manager and a runtime for your application. The necessary packages and references will also be restored prior to the build. Simply add or amend your appveyor.yml file at the root of your project repository with the contents below:
When you self-host your Asp.NET Core web application using Kestrel, it is recommended that you don’t expose it to the outside world, but use a reverse proxy instead. If you followed the sample in cross-platform Asp.NET Core then you found out that your self-hosted application is only available from your local machine. To expose your application to the outside world, the recommended approach is to use a reverse proxy using Apache or nginx.
On Asp.Net Core 1.0 you can create cross-platform applications that will run without modifications in multiple operating systems and CPU’s. Today we are going to create an Asp.Net Core 1.0 “Hello World” sample in Windows and run it in linux (Centos 7.1 x86_64). First we start with the installation of .Net Core 1.0. For Windows, browse to https://get.asp.net/ and download the installer. After running this installer you will be able to run .
Web page performance is very important in a website, as it directly impacts your ROI. A slow website will have a high rate of abandonment and is a source of frustration for your visitors. One of the ways to ensure you are not caught in this situation is to measure web page performance every time you deploy a new feature. To demo this we are going to use: webpagetest.org – The tests will be invoked using its REST API via a Node module Appveyor – A CI service to run the tests First we need to create an API key at webpagetest.
