https://github.com/nrjpoddar/doomsday

Contains sample doomsday microservice application
https://github.com/nrjpoddar/doomsday

Last synced: about 2 months ago
JSON representation

Contains sample doomsday microservice application

• Host: GitHub
• URL: https://github.com/nrjpoddar/doomsday
• Owner: nrjpoddar
• Created: 2017-10-20T15:45:45.000Z (about 7 years ago)
• Default Branch: master
• Last Pushed: 2022-12-07T17:30:03.000Z (about 2 years ago)
• Last Synced: 2023-03-02T00:31:47.769Z (almost 2 years ago)
• Language: JavaScript
• Size: 22.5 KB
• Stars: 0
• Watchers: 1
• Forks: 1
• Open Issues: 2
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## Introduction

Doomsday is a simple application which provides users with current doomsday

time. It uses microservices architecture and is composed of following

microservices:

* *Frontend* - This application exposes the doomsday application to the users. It

communicates with clock microservice to return the current doomsday time back

to users. User requests with any method (GET, PUT, POST or DELETE) to any path

return the same message back to user with 200 OK HTTP status code.

* *Clock* - This application returns the current doomsday time to the frontend

microservice. Currently, the time is statically configured to be `Ten minutes to

midnight`.

### Transaction Logging

Both the microservices currently log the following attributes for every request

received:

* Request Method

* Request URL

* Request Raw Headers as received on wire

* Remote address and port of client

* Local address and port of socket

* Time between receiving the request headers from client and sending last byte

of response back to the client.

### Usage

In order to create this application in kubernetes use the following

instructions:

```bash

kubectl apply -f scripts/doomsday.yaml

```