we may want to use protobuf for web socket communication https://medium.com/@ahmadb/google-protocol-buffers-with-websockets-over-https-in-node-js-express-7ea78157394e.

And before implement it we should check whether we got any advantages by using it

• winston I likely to use it
• where to transport maybe to kafka?
• debug ?

Front-end

• redux-logger

Midleware

• https://www.fluentd.org/

Visualization

• kibana + elastic
• grafana
• graphite
• comparison https://stackshare.io/monitoring-tools

Cloud solutions

• https://rollbar.com/
• sentry
• bugsnag

• reflect middleware actions to redux stream
• messages queue
• reconnect
• overwritable messages move to #58
  examples:

EVIDENCES.SUBSCRIBE -> EVIDENCES.SUBSCRIBE = EVIDENCES.SUBSCRIBE

EVIDENCES.SUBSCRIBE -> EVIDENCES.SUBSCRIBE -> EVIDENCES.UNSUBSCRIBE = 
    null or EVIDENCES.UNSUBSCRIBE

• typeorm
• sequelize

Other comparisons

• Which JavaScript ORM should you be using in 2018?

Additional libs

• https://github.com/hiddentao/squel SQL query string builder for Javascript

We have sources of data in a way of web sockets
And we want to consume this data to Redux state
so our main web app could take new data and reflect it in a right way.
But here comes some questions about pipeline and lifecycle:

• what is the best way to start and stop web socket module?
  For example when we not using chat we don't need flow of incoming messages
  but we could need this flow in few components. So it could make sense to
  trigger on/off module depends on visible components. the Stateful components
  because stateless component doesn't care much about this state.
  So each stateful component could have PubSubModule.start() and
  PubSubModule.stop().
  Another alternative - unbind PubSub Modules from component but bind on state updat
  it could be current visible page, login/logout user and etc.
  So PubSub Module subscribe on state update, and check whether it should start/stop
• Update request to server
  For example our app gets updates depends on our location and user's actions,
  and sure when user walks her location could change so we should update query
  of subscribed data.
  There are few alternatives:

1. call PubSubModule.update(new_params) directly from component
2. subscribe on Redux state change and update when we need it.
   But we should remember previous request and send "diff" only --
   in case of new data.

Challenges

• optimize Redux state subscription. We still can have problem because
  we can't subscribe for specific option. But should react on ant tiny piece update.
  Partly Solution: use libs like reselect
  which store intermediate state tree result so we won't need to go deep
  and extract everything
  we have few alternatives here, to how could we get state for requests:

Architecture

• Should it be middleware?
• Is it another form of UI component?

Websocket as Middleware

it seems middleware is the best way to integrate websockets.

So lets consider Options

• Redux WebSocket Integration - excellent overview of idea of integration ws to redux
• Using socket.io in React-Redux app to handle real-time data. - low code quality, can't recommend
• https://github.com/laumair/resocket
• https://github.com/notgiorgi/redux-websocket-middleware
• and many others

user could see new fire message without any actions from they side

client

• have 2 lists (fetched, stream playlist)
  because we can fetch a lot of items and in different orders. Even in realtime. But playlist should reflect what actually we show to user. #62
• conservative update (show big button that we have N updates) and show updates one click #61
• realtime update load right away #63
• (?) propose realtime update when user stick to the top of page #63 (the same)

• try to find ready made component
• or implement it by myself (example)

• integrate with concov
• travis-ci test for server, static and wss

• https://github.com/zinserjan/mocha-webpack/blob/master/docs/guides/code-coverage.md
• solve error

Module build failed (from ./node_modules/istanbul-instrumenter-loader/dist/cjs.js): SyntaxError: 'import' and 'export' may appear only with 'sourceType: "module"' (1:0)
webpack-contrib/istanbul-instrumenter-loader#33

• https://codecov.io/

similar to this one https://github.com/internetarchive/internet-archive-google-action/blob/master/bin/bump-version.sh

• update version server side code
• update version client side code
• update version of wss
• update tag
• create and commit changelog

• fetched fire evidences (update from wss and fetched directly)
• shown entities (sort, subset of fetched entities)

because we can fetch a lot of items and in different orders. Even in realtime. But playlist should reflect what actually we show to user.

Tools

• How could I support websockets on Nodejs?
  which libs do we have?
• overview
• https://www.npmjs.com/package/ws
• https://www.npmjs.com/package/websocket

• what pm2 gives me, and should I use it in this project?
• should I use pm2 in docker https://github.com/Unitech/pm2/issues/1879 ?
• would I need it with kubernetes? https://github.com/firecast/pm2-docker-kubernetes
  https://speakerdeck.com/georgecrawford/an-introduction-to-docker-and-kubernetes-for-node-dot-js-developers
• integrate with docker http://pm2.keymetrics.io/docs/usage/docker-pm2-nodejs/

• spinner
• estimation of image colors
• grey/color frame if we don't have estimation
• cancel when image disappear

Motivation

we would have few sources of incoming data: nasa images, twitter, instagram, fb and etc.
each source will be consume by some isolated consumer (container) which would process source data and pull result to the queue (stream)

SOURCE -> CONSUMER -> STREAM -> DB -> APP -> CLIENT

So here I'd like to implement scheme of this async stream.
For the moment source of events would be "random fake event generator"

Pipeline

• SOURCE -> CONSUMER Fake event producer
• CONSUMER -> STREAM Setup Kafka
• STREAM -> DB Write Kafka stream to MongoDB
• DB -> APP ❓ Could we subscribe to updates from MongoDB?
• APP -> CLIENT ❓ Could we use WebSockets and scale in the same time? #50

Architecture

• REST API like WebSockets, so we could easily extend Client Server communication with realtime updates (like Sailjs)
• scale: https://hackernoon.com/scaling-websockets-9a31497af051

Generating a self-signed certificate using OpenSSL

• wss

Services

• https://letsencrypt.org/
• chat about it
• https://mozilla.github.io/server-side-tls/ssl-config-generator/

• websockets: React, Redux and WebSocket Unit Testing.

🗺 We have events with coords, and maybe even radius, or even more complex shape.
So we would like to be able to have requests:

• find elements in radius, in screen rectangle in region
• maybe get heat map of events

Options

• postgres + spatial data types
• postgis
• mongodb (http://mongodb.github.io/node-mongodb-native/)

ORMS for spatial data

• postgis + typejs

• front end
• server
• endless stream -> #37
• db

• the main goals
• features which solve goals

extension of #56

examples:
1)

EVIDENCES.SUBSCRIBE -> EVIDENCES.SUBSCRIBE = EVIDENCES.SUBSCRIBE

EVIDENCES.SUBSCRIBE -> EVIDENCES.SUBSCRIBE -> EVIDENCES.UNSUBSCRIBE = 
    null or EVIDENCES.UNSUBSCRIBE

if we get tweet with @fire-marshal or #fire #wildfire
we try:

• get location
• get image
• NLP + tags and categories will be in extra issue

we would have few forms:

• append new fire spot
• user's profile

Alternatives

• formik
• redux-form

standard team doesn't think to support chaijs so I should find work around they recommend to use dirty chai which is obsolete.

plugin https://github.com/ihordiachenko/eslint-plugin-chai-friendly doesn't work out of the box

• get location
• get category
• get extra description
• when it was
• get image

https://github.com/insites/cookieconsent/

• find one design for one landing page
• find place where I could find many designs for other projects 🏭

• message
• categories and tags
• image
• location
• when it was

To give life to this project we should distribute information about it. Any sites, forums, groups where people with similar interests are hanging. Twitter bot. Fb bot. Any ideas?

load more data and append to the current stream (from the end)

more details in PR

• OpenAPI v3 1
  • IMPLEMENTATIONS
  • 10 Resources for Getting Started with OpenAPI 3.0 in 2018
  • Specification
  • Specification 3
• https://github.com/Surnet/swagger-jsdoc integrate jsdoc with open api 3.0
  • Generating documentation on the fly in express

Here we would collect and discuss all similar projects.

Keys:

• what do you like there
• what could be better
• how could we cooperate (API, integrate, etc)

Projects

• British Columbia Wildfire Service

conservative update (show big button that we have N updates) and show updates one click

• eng
• ua
• me/sr
• ru

• show local stream (realtime)
• browser notification (should work on mobile)

• OpenNEX AppStore
  • for challenge
• NASA Fire Information for Resource Management System (FIRMS)
• Incident Information System (INCIWEB database)
• Integrated Reporting of Wildland-Fire Information.
  Data at dispatch speed.

• should we use BSON instead
• lib https://github.com/mongodb/js-bson
• use ws.binaryType = 'arraybuffer'

• could it be React Native? Pros and cons
• can we reuse already existing app
• app architecture design

• get description from NASA site https://2018.spaceappschallenge.org/challenges/volcanoes-icebergs-and-asteroids-oh-my/real-time-fire-app/details
• prioritize my goals
• describe plans

and split docker-compose to both (dev and prod)

❓ how would we simple test both now ❓

• map
• place fires --> #102
• group fires (if many in one point) clustering plugins
• realtime

• How can I implement authentication in Redux?

• ROCKET

The system can recommend nearest safe locations, based on fire spread predictions, mostly by cross-referencing wind direction and speed in the area (Open Weather Map)