Skip to content
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.

doc: update use cases and case coverage #243

Merged
merged 3 commits into from
Oct 2, 2018

Conversation

davisjam
Copy link
Contributor

@davisjam davisjam commented Oct 1, 2018

- Split use cases into "web stack" and "other uses".
- Introduce new use cases based on the Node.js Foundation's
  Application Showcase (https://foundation.nodejs.org/resources/app-showcase)
	and other popular Node.js software I have encountered.
@davisjam
Copy link
Contributor Author

davisjam commented Oct 1, 2018

This PR was inspired by the discussion at the Sept. 18 WG meeting (minutes are in #241).

If anyone is interested, here is a Google Doc with:

  • The 116 Node.js apps listed as of Sept. 2018, plus some others (Micro'15, existing application benchmarks)
  • A preliminary label of the App Showcase apps into one of the use cases
  • A link to its GitHub if the app is open source

I shared a read-only link. If someone else wants to contribute, let me know.

@davisjam
Copy link
Contributor Author

davisjam commented Oct 1, 2018

I have some ideas about workloads to add for use cases. Is this thread a good place to discuss them?

mhdawson

This comment was marked as off-topic.

@mhdawson
Copy link
Member

mhdawson commented Oct 1, 2018

In respect to:

I have some ideas about workloads to add for use cases. Is this thread a good place to discuss them?

I think an issue as opposed to a PR would be a better place for a longer running discussion.

@mhdawson
Copy link
Member

mhdawson commented Oct 1, 2018

@davisjam that is a great list to have along with the classification of the area. Using the Node.js collection is a great idea.

@davisjam
Copy link
Contributor Author

davisjam commented Oct 1, 2018

@mhdawson

Using the Node.js collection is a great idea.

It was your idea ;-)

@davisjam
Copy link
Contributor Author

davisjam commented Oct 1, 2018

I think an issue as opposed to a PR would be a better place for a longer running discussion.

OK. Looks like #6 is a good place to do this.

@davisjam davisjam mentioned this pull request Oct 1, 2018
@davisjam
Copy link
Contributor Author

davisjam commented Oct 2, 2018

@jorangreef

  1. I think you might have some comments on the "systems software" use case and perhaps others?
  2. Where do you think your Ronomon back-end falls among these use cases?

@mhdawson
Copy link
Member

mhdawson commented Oct 2, 2018

@davisjam -> "It was your idea ;-)"

I guess that is why I liked it sooo much even though I forgot that. But thanks for actually putting it into action :)

@jorangreef
Copy link

Thanks @davisjam, replied in #6 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants