pdincau

This is study path related to microservices. It is not a study path on programming, if you want to improve in this sense please take a look at this.

Introductory Videos

• Microservices • Fowler
• Principles Of Microservices by Sam Newman
• Practical Considerations For Microservice Architecture
• Microservices Antipatterns
• When Microservices Meet Event Sourcing

pdincau

Continuous Integration - Know your opportunities

Continuous Integration in a nutshell

Continuous Integration (CI) is an important practice every team should adopt in order to detect defects and errors early and solve integration problems easily. Roughly speaking we may say that CI is a practice that allows the growth of solid software by giving greater confidence to the developers and better products to the final customers.

The concept behind CI is fairly simple: the codebase is owned by several developers that continuously integrate their changes to a common version control system. For each integration the system runs a predefined set of tasks automatically; these tasks may vary from running all the tests to building all the components.

pdincau

Introductions

• Confusion in the land of the serverless • Newman
• Serverless architectures

Nice to have

• What is the fuss about serverless • Wardley

pdincau

Starting point:

* book-service     f4045bf
* book-evaluation  8d47058

Service discovery and multiple instances of book-evaluation:

* book-service     8f22aff
* book-evaluation  master
* eureka-server    master

pdincau

Takeaways from TDD and Software Design

video

• TDD by its own CANNOT leads to good design, obviously
• TDD as a mechanism to help us to learn more about good design
• Software is "Soft" just because it can be changed, it is not meant to be settled in the stone
• Test-first programming can help the team to reduce defects but it will not lead to good design

Code qualities

pdincau

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

pdincau

• Creating a cookbook for our CI server
• Adding a Test Machine
• Automates the application deployment
• Deployment automation in Jenkins
• Logging
• Monitoring
• Cloud infrastructure

Creating a cookbook for our CI server

pdincau

Run tests:

    mix test

Run single test file:

    mix test path/to/file
    
Run single test:

pdincau

Phoenix Ecosystem June 2015

j.mp/phoenix_ecosystem_June2015

Goal of this Document / Gist is to layout the resources and challenges to writing a complete modern web app with Phoenix and Elixir as the state of the projects are starting on June 2015

• [Why Phoenix and not Rails or Node.js?](#Why Phoenix and not Rails or Node.js?)
• Main Resources
• Common Application Requirements
• Authentication

pdincau

sudo -u postgres createdb --locale it_IT.utf8 --encoding UTF8 --template template0 mopapp

postgres -D /opt/boxen/homebrew/var/postgres