Skip to content

Commit 6f4cdc9

Browse files
2 parents 423c3d9 + 47c61ea commit 6f4cdc9

File tree

5 files changed

+6
-236
lines changed

5 files changed

+6
-236
lines changed

README.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
---
2+
services: functions, event-grid, cosmos-db
3+
platforms: dotnet
4+
author: nzthiago
5+
---
6+
17
# Content Reactor: Serverless Microservice Sample for Azure
28

39
In this sample, we have built four microservices that use an [Event Grid](https://docs.microsoft.com/en-us/azure/event-grid/overview) custom topic for inter-service eventing, and a front-end Angular.js app that uses [SignalR](https://www.asp.net/signalr) to forward Event Grid events to the user interface in real time.
@@ -48,8 +54,6 @@ The sample also contains an Angular.js application that is bundled within an ASP
4854

4955
Each microservice and other components within the sample are designed to be built and deployed in a fully automated manner. We used VSTS, although any other build and release management systems could also be used. We used [VSTS's Build YAML](https://docs.microsoft.com/en-us/vsts/build-release/actions/build-yaml?view=vsts) feature to declaratively specify our build process and used [VSTS Release Management](https://docs.microsoft.com/en-us/vsts/build-release/concepts/definitions/release/what-is-release-management?view=vsts) to define our release process and publish the built components to Azure. Please see the `setup.md` file for more information on how to build and release the sample components for yourself.
5056

51-
(TODO Thiago - video could go here?)
52-
5357

5458
# Components
5559

_docs/architecture.png

76.2 KB
Loading

build.sh

Lines changed: 0 additions & 81 deletions
This file was deleted.

deploy.sh

Lines changed: 0 additions & 148 deletions
This file was deleted.

global.json

Lines changed: 0 additions & 5 deletions
This file was deleted.

0 commit comments

Comments
 (0)