Skip to content

Instantly share code, notes, and snippets.

@victorclee
Created July 2, 2017 18:05
Show Gist options
  • Save victorclee/45fc41d5c58a24a814b4385420fc035d to your computer and use it in GitHub Desktop.
Save victorclee/45fc41d5c58a24a814b4385420fc035d to your computer and use it in GitHub Desktop.
Service Oriented Architecture (SOA), Git branches

TIL - Things I Learned - Sunday 07/02/2017

Service Oriented Architecture

The Monolith App - one giant app with different functions
So why individual apps? Easier debugging. If you break one thing in one app, not all other ones break with it.
Think of the sandwich metaphor. The bread, the lettuce, the tomato, the meat, their all edible items by itself. When we put them together, they make a great sandwich, but they are still each great edible items.
Individual apps with shared database probably make more sense! But it also take up more server space, might cost more money.
SOA is also important for having multiple clients.
Which way is better? Should you split your app into microservices?

Git branches

We try not to always make updates to the master branch. Each team can create their own branch.
In order to switch branches, you need to "checkout" the branch you want to be in.
Don't do git push force origin master!!

Useful resource

https://martinfowler.com/articles/dont-start-monolith.html
https://martinfowler.com/bliki/MicroservicePremium.html
https://martinfowler.com/articles/microservice-trade-offs.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment