Educational services departments

This and any subsequent or linked posts are living documents and are subject to change often.

# rework this whole article

Prime candidates for microservices: SIP and CORE

Why is it hard to re-conciliate the two under one schema

This and any subsequent or linked posts are living documents and are subject to change often.

See this post is more of an organizational overview; for the practical difficulties with the current SLATE 1.o schema see this post.

SIP and CORE are described in their own post.

# link to post Educational services departments -> SIP -> CORE

Common ground

Even though

  • they both provide almost the same services and
  • instructors at both departments write lesson notes and progress reports,

they have very different requirements.

Differences

Authorization numbers

At CORE, every single instances of service is assigned a unique authorization number from DOR that is used to keep track of notes, reports, billing etc.

SIP does not have a notion of authorization number and it operates through grants.

Services

Teach the same four basic blindness skills but as part of retreats and in-home visits without using authorization number so distribution of instructional units differs greatly.

Billing

CORE does monthly billing towards DOR
 while
 SIP has to submit monthly and quarterly reports towards our grantor plus the yearly grant-writing process with all the information aggregated.

Conclusion

The departments use very similar schemas but the above differences make it hard(er) to re-conciliate differences in one monolithic application. That is the plan though which is going to be a good exercise but will follow up with a microservices solution once I get there.

# follow up with microservices