2022-08-10 Meeting notes

1 min

Scribe

All

@Ankita Sen is next followed, by @Jakub Skoczen 

-

TCR Board Review

All

Nothing to review

10-15 min

Technical Council Sub Groups Updates

All

• Technical  council goals/objectives:

  • @Tod Olson - next meeting dates are being decided(tentative date: Monday,15.08.2022) and there has been planning about WOLFCON, @VBar and @Tod Olson  have been creating on creating an architectural blue print agenda for Wolfcon. Next checkin 24.08.2022 

• Breaking Changes :

  • @Jeremy Huff - met this week and discussed about what constitutes as not a breaking change with respect to backend modules and about breaking changes for interfaces. Good progress made on deicing the various breaking changes. Next step is to start producing the deliverables

• Elasticsearch vs Opensearch: 

  • @Marc Johnson - not much progress except a few points of discussion in the slack channel.

• Controlling AWS Hosting:

  • @Mark Veksler - Met last week and drafted a cost management report that is likely to be received. A spike story was created for the Kitfox team on how to track the AWS resources that can be made into the report. Kitfox team will require a sprint or two to get this Spike started(?) and the subgroup is meeting again onFriday(12.08.2022) to discuss further steps.

-

RFCs

All

Nothing to review 

10-20 min

Cross-App data sync

@Raman Auramau 

Previous Notes from presentation last week:

• Presentation (15m-20m) & Q/A (10m): Data sync updates and outcome (TC)

• Looking for solutions that are generally applicable and preserve loose coupling between modules

• Changes in source of truth are to be done atomically, and then notifications sent to consumers

• Details in proposal FOLIO Cross-Application Data Sync Solution

• Proposal is already in use in inventory, changes in mod-inventory-storage  send notifications to be consumed by mod-search 

• Q&A:

  • The message passing via Kafka introduces dependencies between modules. Do we have a mechanism for documenting / declaring the dependencies. Discussed, but intentionally out-of-scope for the group.

  • Are there guidelines on how retention period may change? Trade-offs, retention periods may be different based on use case, no one approach for all cases. Deliberately does not allow for replay.

  • Full-body vs. diff message: there are message sizes, and Kafka works better for small events. 10-100KB cover current known use cases.

  • Regarding outbox pattern, was the Debezium idea evaluated? No, just came up in brainstorming.

    • Debezium is used in LDP/Metadb. Debezium/WAL solutions do generate A LOT of events, which heavily impacts Cloud hosting costs.

  • Are there performance issues with Outbox pattern? Did not do specific testing, existing uses do not have numbers, but also did not state concerns about performance. Outbox will introduce some delay in notifying consumer. Different use cases have their own acceptable delays.

  • Do we need to propose a mechanism for synchronizing data in cases where events get lost.

  • What are next steps? This process pre-dates ADR/RFC process.

    • Action: group will create and ADR and ask for TC approval

    • POC & performance testing? existing work in inventory could be considered POC, but do not use Outbox pattern.

    • Can discuss next steps after TC approval

  • Group was starting from current state of FOLIO and current use cases, was working from a more constrained view than green field.

  • Current reindexing approach undermines some of the is proposal, relies upon consumer knowing the source of truth. 

Today:

< 5 min

Quarterly Community Update

@Craig McNally 

The next Quarterly Community Update is approaching (last day of WOLFcon).  I will be pulling together lists of accomplishments, goals, etc. soon.  Please let me know if you have any ideas/thoughts.  Once I have something I will share it at an upcoming TC meeting.

Remaining Time

Other topics

All

Several topics have been raised recently that deserve attention/discussion.  The goal here is to figure out how to best move these forward, without digging into the topics themselves.  Is there a priority here?  Should we spin up working groups for any of these?  etc.

• Ease of installing/deploying FOLIO - @Ian Walls , @Marc Johnson , @Jeremy Huff

  •  Primary task the Tc would take on by making FOLIO easier to get up and running. Would also reduce AWS costs so that the money coming from Membership groups can be flowed to other aspects of FOLIO. Tc is the best equipped group to decide on how to make installing and deploying Folio easier and cheaper.

  • @Craig McNally - Brainstorming open ended session with @Ian Walls and then discuss further before or after Wolfcon depending on the brainstorming session. @Ian Walls and @Tod Olson to frame the topics of discussion for the brainstorming. 

• Revisiting FOLIO Governance 

  • @Ian Walls - should be best discussed in cross council meeting possibly at Wolfcon. Idea to was bring this up at a high community level not necessarily the Pc or TC. Doesn't need to be on TC agenda next week. Aspects to be discussed at Wolfcon.

  • See also:  messages to PC and CC councils

• How/when to make significant technology changes in coordination with the release schedules of other tools, e.g. keeping in sync with Node LTS releases, or Java 17 or Postgres 14, etc. 

  • May be overlapping with the Tools/dependency versions

  • @Marc Johnson - It would be useful to relate the changes to match the release schedules

  • See also:  messages in TC channel

  • On agenda next week along with Tools/Dependency version

• Tools/dependency versions - @Vijay Gopalakrishnan took on this topic as a project. There is also a proposal Managing Tools/Framework Dependencies currently in Draft stage with feedbacks as latest as 02.08.2022. On agenda for next week.

• @Jakub Skoczen - Planning about Wolfcon working sessions? How to run the sessions? Put this on the agenda next week.