Fork me on GitHub
#ldnproclodo
<
2016-04-19
>
agile_geek16:04:55

ProCloDo at CodeNode, SkillsMatter, starts at 6:30pm tonight.

agile_geek17:04:21

Just gathering..]

agile_geek17:04:35

haven't done silly question yet!

agile_geek17:04:08

Silly question is: Microservice or Monolyth?

otfrom17:04:43

that's a good one

otfrom17:04:56

or microlyth or monoservice

otfrom17:04:08

micormono or servicelift?

otfrom17:04:24

majordomo or service lift

agile_geek18:04:49

No - Microservice or Monolyth!

agile_geek18:04:55

You can't dodge it

agile_geek18:04:49

Just talking about the format for the meeting.

agile_geek18:04:39

I think the consensus is around deciding on discrete problems/issues to take away and tackle then coming back next month with a PR

agile_geek18:04:59

Just demo'ing the app and walking thru structure atm

otfrom19:04:14

microservice

agile_geek21:04:59

So I will write up my interpretation of the new format of ProCloDo and post it here and also add it to either the readme or the wiki in github when I get a chance

agile_geek21:04:02

In the meantime here is a summary of the design decisions taken in this meeting:

agile_geek21:04:01

1. Leave petrol as the cljs approach for now to maintain some stability in the codebase for a few months - to review at later date

agile_geek21:04:14

2. Stick with the current 'post a map to a single uri' approach to server requests rather than REST for now. Again to maintain some stability in the code base.

agile_geek21:04:45

3. Look to implement a few of the trello cards around functionality over next month.

agile_geek21:04:30

4. implement authorisation and authentication over next month or so.