{"id":18614202,"url":"https://github.com/evalle/poms","last_synced_at":"2026-04-30T09:31:46.097Z","repository":{"id":76969481,"uuid":"89072281","full_name":"Evalle/POMS","owner":"Evalle","description":"The main ideas from the \"Principles of Microservices\" course","archived":false,"fork":false,"pushed_at":"2017-04-25T11:36:40.000Z","size":35,"stargazers_count":1,"open_issues_count":0,"forks_count":2,"subscribers_count":1,"default_branch":"master","last_synced_at":"2024-12-27T02:43:28.036Z","etag":null,"topics":["cd","continuous-delivery","design","devops","docker","kubernetes","microservice","microservices","principles"],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Evalle.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-04-22T13:37:20.000Z","updated_at":"2017-05-17T19:42:39.000Z","dependencies_parsed_at":"2023-02-27T05:45:41.628Z","dependency_job_id":null,"html_url":"https://github.com/Evalle/POMS","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Evalle%2FPOMS","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Evalle%2FPOMS/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Evalle%2FPOMS/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Evalle%2FPOMS/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Evalle","download_url":"https://codeload.github.com/Evalle/POMS/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":239406447,"owners_count":19633024,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cd","continuous-delivery","design","devops","docker","kubernetes","microservice","microservices","principles"],"created_at":"2024-11-07T03:25:32.492Z","updated_at":"2025-11-03T03:30:22.553Z","avatar_url":"https://github.com/Evalle.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# POMS\nThe main ideas from the [\"Principles of Microservices\"](http://shop.oreilly.com/product/0636920043935.do) course\n\n## Table of Contents\n1. [Introduction](#introduction)  \n2. [Advantages of Microservices](#advantages-of-m)\n3. [Disadvantages of Microservices](#disadvantages-of-m)\n4. [Principles of Microservices](#principles-of-m)\n   - [Modelled around Business Domain](#modelled-around-business-domain)\n   - [Culture of automation](#culture-of-automation)\n   - [Hide implementation details](#hide-implementation-details)\n   - [Decentralise all the things](#decentralise-all-the-things)\n   - [Deploy independently](#deploy-independently)\n   - [Consumer first](#consumer-first)\n   - [Isolate failures](#isolate-failures)\n   - [Highly observable](#highly-observable)\n5. [When YOU should use Microservices](#when-you-should-use-m)\n6. [Useful Books](#useful-books)\n\n### Introduction\nThe Microservices (M) are small, **autonomous** services that work together\n*Small* here means that they're doing one thing well. \nThe Microservices are just one of the implementations of Service Oriented Architecture (SOA)\n\n### Advantages of M\n - better allignment with the organization\n - ship faster\n - independent scaling\n - enable segregation models\n - adopt technologies more easily (you can use different languages/technologies for each M.)\n \n### Disadvantages of M\n  - lots of options (can be as the Advantage or the Disadvantage)\n  - it takes a lot of time to get into M. \n  - testing of M. is more complex \n  - monitoring and investigation of failures is more complex\n  - resiliency isn't free\n  - disrtibutes systems are hard! - with Monolith you have a binary state - it's up or down, with M. some of your services can be down,\n  another - up and running.\n  \n### Principles of M\n  1. Modelled around business domain\n  2. Culture of automation\n  3. Hide implementation details\n  4. Decentralise all the things\n  5. Deploy independently\n  6. Consumer first\n  7. Isolate failure\n  8. Highly observable\n\n### Modelled around Business Domain\n[Presentation] -\u003e [Business Logic] -\u003e [Data Access] - jst a simple example.\n\n### Culture of Automation\n- Continous Delivery (build -\u003e test -\u003e UAT -\u003e prod)\n- API - driven machine provisioning (creating a new node via API), see [AWS](https://aws.amazon.com/), [Digital Ocean](https://www.digitalocean.com/), [OpenStack](https://www.openstack.org/), [Vagrant](https://www.vagrantup.com/), etc\n- API - driven OS configurationm, see [Chef](https://www.chef.io/chef/), [Puppet](https://puppet.com/), [Ansible](https://www.ansible.com/) \n- Custom image creation, see [Packer](https://www.packer.io/)\n- Declarative environment provisioning, see [Docker Compose](https://docs.docker.com/compose/), [Terraform](https://www.terraform.io/)\n- Automatic testing\n\n### Hide implementation Details\n- Hide your DB!\n- Think about protocols: YAML. JSON, XML, SOAP\n- Be careful of client libraries\n\n### Decentralise all the things\n- internal open source model, see [Gitlab](https://about.gitlab.com/)\n- orchestration\n- self-service\n- owner operator (each team is the main operator of their piece of software)\n\n### Deploy Independently\n- One service per OS/VM/Container\n- Consumer-driven contracts, see [Pact](https://docs.pact.io/)\n- Co-existing service versions\n- Multiple enpoints (e.g. another API version of the same service)\n\n### Consumer First\n- Conversations\n- Consumer-driven contracts, see [Pact](https://docs.pact.io/)\n- Standards, see [PayPal API standards for example](https://github.com/paypal/api-standards/blob/master/api-style-guide.md)\n- API documentation, see [Swagger](http://swagger.io/)\n- Service Discovery, see [Consul](https://www.consul.io/), [etcd](https://coreos.com/etcd/docs/latest/), DNS\n\n### Isolate Failures\n- M. aren't reliable by default\n- Cascading failures can hurt\n- Timeouts\n\n### Highly Observable\n- Standrad monitoring\n- Service monitoring, see [docker stats](https://docs.docker.com/engine/reference/commandline/stats/), [collectd](https://collectd.org/)\n- Health check pages\n- Log aggregation, see [Logstash](https://www.elastic.co/products/logstash), [fluentd](http://www.fluentd.org/), [kibana](https://www.elastic.co/products/kibana) \n- State aggregation, see [Graphite](https://graphiteapp.org/)\n- Semantic monitoring (for example try to mock user actions each 5 minutes)\n- Correlation ID (every action with ID, so you can catch it on every M. logs by this ID)\n\n### When YOU should use M\n- What are you looking for?\n- What kind of problem from the M. advantages are you trying to solve?\n\n### Useful Books\n1. [\"Building Microservices: Designing Fine-Grained Systems\"](http://shop.oreilly.com/product/0636920033158.do?cmp=af-code-books-video-product_cj_0636920033158_7739078) by Sam Newman\n2. [\"Continuous Delivery\" ](https://www.amazon.com/dp/0321601912?tag=contindelive-20) by Jez Humble\n3. [\"Domain-Driven Design\"](https://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215) by Eric Evans\n4. [\"Service-Oriented Architecture (SOA): Concepts, Technology, and Design\"](https://www.amazon.com/Service-Oriented-Architecture-SOA-Concepts-Technology/dp/0131858580) by Thomas Erl\n5. [\"I Heart Logs: Event Data, Stream Processing, and Data Integration\"](https://www.amazon.com/Heart-Logs-Stream-Processing-Integration/dp/1491909382/ref=sr_1_1?s=books\u0026ie=UTF8\u0026qid=1493119886\u0026sr=1-1\u0026keywords=i+heart+logs) by Jay Kreps\n6. [\"Infrastructure as Code: Managing Servers in the Cloud\"](https://www.amazon.com/Infrastructure-Code-Managing-Servers-Cloud/dp/1491924357/ref=sr_1_1?s=books\u0026ie=UTF8\u0026qid=1493119925\u0026sr=1-1\u0026keywords=infrastructure+as+code) by Kief Morris\n7. [\"The Art of Scalability: Scalable Web Architecture, Processes, and Organizations for the Modern Enterprise\"](https://www.amazon.com/Art-Scalability-Architecture-Organizations-Enterprise/dp/0134032802/ref=sr_1_1?s=books\u0026ie=UTF8\u0026qid=1493119985\u0026sr=1-1\u0026keywords=the+art+of+scalability) by Martin L. Abbott\n8. [\"Release It!: Design and Deploy Production-Ready Software (Pragmatic Programmers)\"](https://www.amazon.com/Release-Production-Ready-Software-Pragmatic-Programmers/dp/0978739213/ref=sr_1_1?s=books\u0026ie=UTF8\u0026qid=1493120112\u0026sr=1-1\u0026keywords=design+and+deploy+production+ready) by Michael T. Nygard\n9. [\"Production-Ready Microservices: Building Standardized Systems Across an Engineering Organization\"](https://www.amazon.com/Production-Ready-Microservices-Standardized-Engineering-Organization/dp/1491965975/ref=asap_bc?ie=UTF8) by Susan J. Fowler\n\n\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fevalle%2Fpoms","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fevalle%2Fpoms","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fevalle%2Fpoms/lists"}