General timing, partners, SoWs, etc all relating to what's happening with the re-architecture. Shooting for MVP/beta in October 2016, with 3.0 in Feb 2017.
5 min
Re-Architecture Document
Josh
Last week we hinted about it. Hopefully since then we've had a chance to read it and think about it. I'll quickly go over the high-level pieces to & hopefully we can discuss on the forums.
How is the database handled? A: each service owns its own schema. DB access is passed to service via configuration
What about interaction between services? A: The service's RESTful interface should be complete and sufficient for all clients, whether it is programmatic, a desktop UI, a mobile client, etc.
Chongsun presented results of "extra data" spike, mainly, how to store additional data that a particularl client may wish to add to existing entities. E.g. adding "color" to a Facility
JSON option. Postgres supports JSON datatype, even simple querying. Can set and get values and set up static queries
"thin tables" opion.
Pengfei suggested a third - a document database, and offered to do a spike
Chongsun showed the Independent Service template beginnings.