Diego Pacheco Tech blog

Dear reader, you might miss my post on the last 7 months. I was not posting with the same frequency I was doing before. The reason why it happened is because I was written a book about Scala. I'm here to announce my very first book about building Scala application. The book goes for the basic principle of functional and reactive programming to the most advance scala language ecosystem solutions such as Play Framework, Akka Framework, RxScala and much more.  I hope you enjoy the book and hope this book could help you in your career building scalable and modern scale applications. You can buy the book here: https://www.amazon.com/Building-applications-Scala-Diego-Pacheco/dp/178646148X Cheers, Diego Pacheco

Netflix Dynomite is Kick Ass Generic Dynamo implementation for K/V Stores. Recently Netflix released the Dynomite-Manager  at he NetflixOSS Meetup Season 4 Episode 2 . Dynomite and Dynomite-Manager are Rock Solid both are a beautiful piece of engineering work. Dynomite has High Throughput and Low Latency. It gives superpowers to Redis making him Strong Consistent with Quorum like semantics and multi-datacenter.  It's possible to use Dynomite as Cache or as a Data Store.

This was the second consecutive year, I do lectures at QCon Sao Paulo. Las year(2015) I was talking about DevOps . This year(2016) I was talking about my experiences with the Netflix Stack for building Reactive Microservices with Java 8. The talk is available here .

Boto3 is a kick ass AWS client for python. If you are working as a DevOps Engineer with Cloud that's a library you must check it out. Boto3 improved a lot the design in comparison with boto2. For this blog post, I will show how to do 2 simple things but yet very powerful things. Besides boto, I will show how to use Paramiko  another cool library in Python which can manipulate SSH and connect to boxes and perform commands. You will need to have an AWS account and you SECRETS in hand in order to make the code work. You can use python 2 or python 3 both can work with boto3.

On the previous posts of the series Telemetry and Microservices part 1 and part 2  I described the desired features of a modern observability / telemetry platform should target to address microservices monitoring needs. I've also blogged about Alerting and monitoring with Sensu part 1 and part 2 .  For this post, I will cover some components of the open source telemetry landscape which you can take advantage of your microservice monitoring architecture. For this blog post I will be talking a little bit more about the following solutions: 1. Sensu 2. Prometheus 3. OpenTSDB 4. Netflix Atlas 5.  Riemann 6. Graphite

June 1st, 2016 I will be speaking about my experiences with NetflixOSS and Dynomite at the Season 4 Episode 2 Netflix meetup. You can check out some posts I did about the NetflixOSS stack: http://diego-pacheco.blogspot.com/2015/09/netflixoss-devops-stack-for.html http://diego-pacheco.blogspot.com/2015/11/netflix-dynomitedyno-cluster-for-redis.html There are POCs and code samples available in my Github which you can check it out here .  Cheers, Diego Pacheco

This is the second blog post about Sensu as an Alerting and Monitoring solution. If you did not read the first part I recommend you check it out here . For this blog post, I will share a Vagrantfile so you have run sensu in your machine easily.  To play with Sensu you need to have some components like:  * A sensu Client  * A sensu Server  * RabbitMQ  * Uchiwa for Sensu Server TLDR;  Check it out all file in my GitHub account .