https://github.com/misaelnieto/json_eav_example

A web app with EAV pattern and JSON API
https://github.com/misaelnieto/json_eav_example

Last synced: 1 day ago
JSON representation

A web app with EAV pattern and JSON API

• Host: GitHub
• URL: https://github.com/misaelnieto/json_eav_example
• Owner: misaelnieto
• Created: 2018-09-19T20:52:40.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2018-09-19T21:40:47.000Z (over 6 years ago)
• Last Synced: 2024-11-11T11:11:53.643Z (2 months ago)
• Language: Python
• Homepage:
• Size: 13.7 KB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# The Risk application

I started this application as a hiring project and quickly became a ground test for me to try all new technologies on 2018.

Here's the challenge:

> An insurance company used to manage their risks as primary property-based (homes, farms, churches, etc.), so their data model is very rigid since assumed that all the risks are properties and have addresses. Now they want to work with other kinds of risks like Cars, Cyber Liability Coverage (protection against hacking), or Prize Insurance (if someone gets a $1 million hole-in-one prize at a golf tournament, the golf course doesn't pay it, they have an insurance policy to cover them).

So, they need to have a dynamic data model. They want to avoid to add a table everytime they come up with a with a new Risk type. 

Q: How to solve this in a civilized way?

A: This looks like a good fit for Entity Atribute Value (EAV) pattern.

## Current state:

Backend:

- [x] Select the framework for the backend (Django + Postgresql + Django REST Framework).

- [x] Django installed and configured.

- [x] Core data model.

- [ ] JSON API Backend.

Frontend:

- [ ] Decide framework

- [ ] Basic Auth

- [ ] Single Plage App using selected framework