Skip to content
MagusMachinaePublic

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Repository files navigation

Polylith documentation can be found here:

You can also get in touch with the Polylith Team via our forum.

BurnUp

BurnUp is a proof-of-concept/toy-model for a contracting/job site for the energy industry. The backend is written in Clojure using polylithic architecture and complies with the RealWorld API spec. The app is largely built around the Compojure library, with the Luminus framework used sparingly. Because of the RealWorld spec, it can be paired with any similarly implemented front-end. However, for the purposes of this PoC, the front ends for mobile and desktop devices will be written in ClojureScript, targeting Native and React frameworks through wrappers.

Frontends

Frontends to be implemented once core systems of backend are functioning

Installation

Implementation Details

  • Users: A user can either be a contractor or an organisation. While the implementation does not explicitly use inheritance, Clojure and Datomic are flexible and fine-grained enough to allow them to be distinct "classes" without complicating behaviours such as logging in. To expand on the example, on log-in the database is queried for all user nodes with a matching username-password pair, without needing to distinguish between the two types of user, and serves the relevant usertype-specific resources once the user type is checked after authentication. Components can inherit from each other like classes in a loose sense via dependencies. Class hierarchy is also implemented in this fashion.
    • Contractor: Has a profile with employment details such as rate etc., may tender proposals to contracts.
    • Organisation: Has a more limited profile with company contact details, may generate contracts. May be further expanded to distinguish between operators and service providers.
  • Contracts: Generated as a node with an edge to the generating organisation. When a proposal is accepted, an edge from the contractor to the contract is generated.
  • Proposals: Generated by contractors and must be associated with an existing Contract node.
  • Database: Graph Database implemented in Datomic. For development purposes, and to make demonstration easier, the database itself is run entirely as an anonymous instance in memory. Schemata and seeded database entries are loaded in from a .edn file on launch.
  • Instant Messaging System: Potential feature. Initial implementation would be limited to communication between contractors and organisations during contract negotiation and for active projects

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages