Fyre - Revision history

Dereckson: Fyre cat

2024-10-26T20:38:31Z

Fyre cat

← Older revision		Revision as of 20:38, 26 October 2024
Line 17:		Line 17:
	* Artefacts can be described as classes, and this description can include how they can be stored		* Artefacts can be described as classes, and this description can include how they can be stored

	[[Category:Fyre]]		[[Category:Fyre\|*]]

Dereckson at 20:38, 26 October 2024

2024-10-26T20:38:25Z

← Older revision		Revision as of 20:38, 26 October 2024
Line 17:		Line 17:
	* Artefacts can be described as classes, and this description can include how they can be stored		* Artefacts can be described as classes, and this description can include how they can be stored

	[[Category:~~Projects~~]]		[[Category:Fyre]]

Dereckson: +cat, context, proofreading

2024-10-26T13:22:18Z

+cat, context, proofreading

← Older revision		Revision as of 13:22, 26 October 2024
Line 1:		Line 1:
			'''Fyre''' is the project idea name to build an ecosystem of components for personal life.

	== Goals ==		== Goals ==
	* Track items (packages, books, music albums)		* Track items (packages, books, music albums)
Line 13:		Line 15:
	* Items can be grouped in collections by type, allowing to choose storage for each type		* Items can be grouped in collections by type, allowing to choose storage for each type
	* Index of items is another problem and can be solved whatever storage is used for items - e.g. ElasticSearch or [https://github.com/valeriansaliou/sonic Sonic]		* Index of items is another problem and can be solved whatever storage is used for items - e.g. ElasticSearch or [https://github.com/valeriansaliou/sonic Sonic]
	* ~~Artifacts~~ can be described as classes, and this description can include how they can be stored		* Artefacts can be described as classes, and this description can include how they can be stored

			[[Category:Projects]]

Dereckson: /* Storage */

2020-03-02T16:43:22Z

Storage

← Older revision		Revision as of 16:43, 2 March 2020
Line 12:		Line 12:
	== Storage ==		== Storage ==
	* Items can be grouped in collections by type, allowing to choose storage for each type		* Items can be grouped in collections by type, allowing to choose storage for each type
	* Index of items is another problem and can be solved whatever storage is used for items - e.g. ElasticSearch or [https://github.com/valeriansaliou/sonic Sonic		* Index of items is another problem and can be solved whatever storage is used for items - e.g. ElasticSearch or [https://github.com/valeriansaliou/sonic Sonic]
	* Artifacts can be described as classes, and this description can include how they can be stored		* Artifacts can be described as classes, and this description can include how they can be stored

Dereckson: Created page with "== Goals == * Track items (packages, books, music albums) * Store artifacts for those items (e.g. stuff ordered, invoices for those) * Flexible architecture to be composed as..."

2020-03-02T16:42:12Z

Created page with "== Goals == * Track items (packages, books, music albums) * Store artifacts for those items (e.g. stuff ordered, invoices for those) * Flexible architecture to be composed as..."

New page

== Goals ==
* Track items (packages, books, music albums)
* Store artifacts for those items (e.g. stuff ordered, invoices for those)
* Flexible architecture to be composed as people wants in their own apps

== Architecture ==
* Storage back-ends: store locally tracked items, and artifacts for those items
* Agents to perform tasks to see how the status of a tracked item evolves (e.g. for a delivery pending -> delivered)
* Libraries to connect with external services and parse results: an API client or a web site automated client
* Reactors ("if this then that") to generate a new event when an event is done (e.g. order -> delivery -> acceptance or returns)

== Storage ==
* Items can be grouped in collections by type, allowing to choose storage for each type
* Index of items is another problem and can be solved whatever storage is used for items - e.g. ElasticSearch or [https://github.com/valeriansaliou/sonic Sonic
* Artifacts can be described as classes, and this description can include how they can be stored