Simple Dev-Ops

The best explanation for me(so far) about DevOps

Ops – it operates the application in production
That is, it assure service uptime and availability(responsiveness)

### Deploy to produciton

### Monitoring (for service uptime/availability)
– if the service is down, it will restart it
– if the machine/server is going crazy(if there is high load, no disk space, etc..), it will alert, intervene, solve, investigate
– if the application throws a lot (of unexpected) errors/exceptions

### Service responsiveness
– scaling, add a new node

Later Update

Another Great image found on Dzone

 

 

microservices-architecture-challenge-advantage-drawback

The best article on this topic so for.

Microservices Architecture: Advantages and Drawbacks

Clear definition:
Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs).

Strafulgerare, sync communication:

In this video we can see this picture

Monolith:
And the author says that the communication passes synchronously from top to bottom and then back in the reverse

But as you can see in the picture, even in a microservices architecture, you still have sync communication… but you call an REST Endpoint and you (block)wait for the response before you can go further with your program execution

Pyramid of Refactoring – clear flow

Pyramid of Refactoring

…before you finished dealing with clear sequential flow
Clear flow means that you are able to read and understand your code easily and quickly. This means that it doesn’t contains things like mysterious field / variable names, (deeply) nested conditions and loops.