2016-05-03 Meeting notes

Date

May 3, 2016 PDT & EDT

4-4:50pm PDT

7-7:50pm EDT

20 Apr 2016 7-7:50am Beijing / CST

Join by phone:
Dial phone number and enter the Meeting ID (30957362) when prompted
- Toll: +1 201-479-4595

Time	Item	Who	Notes

Time	Item	Who	Notes
2 min	Community Survey	@Rich Magnuson (Deactivated)	Please contribute to the survey - see https://groups.google.com/forum/#!topic/openlmis-dev/6nNjYxy-ZqE
	Re-arch updates	Rich	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.
15 minutes	Re-architecture Design - ExtraData	@Chongsun Ahn (Unlicensed)
15	Service Template - Design?	@Chongsun Ahn (Unlicensed)
	Community updates?

Briefly reviewed high level architecture document overview. Some Q&A:
- 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.

@Pengfei Cui (Deactivated) - spike on document database