ivo's home

Quote:

Benchmarks range wildly here, from Scaleway’s performance being “only somewhat worse than DigitalOcean” to “much worse” to “catastrophic”. 

Source:

https://blog.rebased.pl/2015/11/04/scaleway-vs-digitalocean.html

my other side: ivo.blogspot.com

This interesting article from DZone explores why in some cases microservices actually become a burden and reverting back to monolith instead can be the solution.

In early 2017, we reached a tipping point with a core piece of Segment’s product. It seemed as if we were falling from the microservices tree, hitting every branch on the way down. Instead of enabling us to move faster, the small team found themselves mired in exploding complexity. Essential benefits of this architecture became burdens. As our velocity plummeted, our defect rate exploded.

Eventually, the team found themselves unable to make headway, with 3 full-time engineers spending most of their time just keeping the system alive. Something had to change. This post is the story of how we took a step back and embraced an approach that aligned well with our product requirements and needs of the team.

Goodbye Microservices: From Hundreds of Problem Children to One Superstar

my other side: ivo.blogspot.com

James Higginbotham describes nine things to consider when you decide to run docker in production servers.

Developers need to remember that Docker is a tool, not a full-blown cloud native architecture solution. It offers some amazing capabilities, and I’m very happy to have Docker as part of my architecture. But it requires the same effort to maintain a production Docker deployment as any other cloud-based solution (and perhaps even more).

Read more here.

my other side: ivo.blogspot.com

# ss -n |grep ESTAB |wc -l
13615

# ss -n |grep CLOSE-WAIT |wc -l
10832

# ss -n |grep FIN-WAIT |wc -l
1976

# ss -V
ss utility, iproute2-ss061002

my other side: ivo.blogspot.com