Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

2 notes #265

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

2 notes #265

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions service_oriented_design/group_notes/group_2.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Small Group Discussion of "Service-Oriented Design"

### Group

Group members: Austen, Andy, JQ, Elise

### Discussion Summary

#### How do the techniques and advice map to the design decisions you've made in your individual projects? How have you veared away from them? Has this been for good or ill?

We've implemented the user model from chapter one, but are running into issues with auth. We are splitting up our databases like he talked about in the book. The folks that have done rails have been moving along more speedily than those who are trying to implement sinatra.

#### What is the lifecycle of a new chat message in your system? Compare this across projects. Are there differences; if so, why, and what impact does that have on the overall system design?

Group 2 (Austen) :

Client -----> OctoChat Chat Server
|
^ Message Queue
|----------------------|---------------------> Search Service and Data Service

JQ:
Messages service - then persistence, new message from Faye