2016-05-03 Meeting notes

Date

  PDT & EDT

4-4:50pm PDT

7-7:50pm EDT

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

http://fuze.me/30957362

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

Attendees

Goals

  • Updates on re-architecture
  • Community survey

Discussion items

TimeItemWhoNotes
2 minCommunity Survey

Please contribute to the survey - see https://groups.google.com/forum/#!topic/openlmis-dev/6nNjYxy-ZqE

 Re-arch updatesRichGeneral 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 minRe-Architecture DocumentJosh

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 minutesRe-architecture Design - ExtraData 
15Service Template - Design? 
 Community updates?  

Notes

  • 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.  

Action items

OpenLMIS: the global initiative for powerful LMIS software