devops

Recursos de programación de devops
En esta charla vamos a recordar el problema de hacer una entrega de software, vamos a despiezarlo y a proponer unas prácticas que encajan en el ámbito de Devops. Analizaremos esas prácticas desde el punto de vista de los principios de Lean Software Development: * Eliminar el desperdicio * Crear conocimiento * Decidir lo más tarde posible * Hacer la entrega lo más rápido posible * Hacer valioso al equipo * Calidad, sin errores * Optimizar el total Y uniremos este análisis con la economía de desarrollo de software, nos pondremos el sombrero de economistas y hablaremos de riesgo, time to market, coste, valor o deuda para finalmente comprobar que son rentables si las vemos desde el punto de vista del dinero. También estudiaremos cómo la carencia de una determinada práctica afecta a nuestro negocio, ¿qué pasa si tenemos caído nuestro negocio durante una hora?¿Cuánto vale eso?
Este pasado 1 y 2 de diciembre, asistí a la CAS2016, la conferencia agile spain en Siberia-Gasteiz.Agile Spain organiza dos eventos principales cada año, el AOS y la CAS, y tengo que reconocer que yo soy de esos a los que siempre le hace más ilusión el AOS, principalmente porque el ambiente suele ser más de reunión para compartir que de conferencia. Por otro lado, había tenido alguna experiencia algo regular con alguna de las CAS anteriores, en las que me parecía que una parte de las presentacio...
One year ago I started to work at TheMotion and at the same time I decided to recover my previous reading habit. I also discovered the audio books that are a very good choice for me, because I go for a walk (1-2h) every day... The only problem is that not all the books that I like are in this format....In any case, these are the books I have read / heard during this time at TheMotion...The Power of Habit: Why We Do What We Do in Life and Business. Charles Duhigg   (Pending review)...
Getting DevOps right isn't easy. It's downright hard. In this talk, I'm not going to explain how to 'do' DevOps in your organisation, since there is not just one 'right' way to do it. What I can show you however, is how NOT to do DevOps. This session shares 15 common misconceptions, call them anti-patterns, of DevOps. I'll talk from my own experiences in getting things wrong, explain why they are wrong and prevent you from making the same mistakes. You'll leave this session with a basic understanding of how (not) to fail at DevOps and hopefully, a smile on your face ;-)
Vert.x is a toolkit for building reactive applications on the JVM. It's event driven, non blocking and polyglot, which makes it an excellent platform for building microservices. In this talk, I'll share experiences and from a Dutch company that started building reactive web applications with Vert.x about 3 years ago. You'll learn the concepts behind Vert.x, why we chose Vert.x, how we're using it and the challenges we faced. Topics include the anatomy of our projects, (micro)services architecture, deployment model and DevOps, scalability and the upgrade from Vert.x 2 to Vert.x 3.
It's a talk about the new serverless architecture movement that is happening using new technologies like AWS Lambda, API Gateway and DynamoDB. This new way of building architectures opens up a whole new dimension of scalability and cost effectiveness. By using microservices that run in AWS Lambda functions, you literrally pay 0 euro when your code doesn't execute. As an added benefit you won't have to deal with devops, so no server configuration or security updates.
This are some interesting talks/podcasts/presentations about DevOps and Agile culture that I watched during June and July:#NoStaging - PIPELINE Conference 2016 Dave Nolan. Should we use always a staging environment? Of course, it depends on the context... We  should always evaluate continuously any practice that we are using. Including having a staging environment. A lot of teams have one, but perhaps not all of this teams have a clear idea about the costs and the benefits.Ho...
To make applications more portable without the heavy redesign during migration remains to be one of the main DevOps goals. In some cases, the unaffordable complexity during migration requires a significant redesign of existing legacy applications. However, stateful containers can simplify the migration task drastically. With the help of stateful containers IT companies are able to migrate legacy Java applications with zero code change making some minor or even no adjustments. After migration, engineers will be able to improve the architecture of the legacy applications by decomposing monolithic architecture to multiple containers or even to microservices. In the future that will allow to easily redesign stateful applications to stateless by moving state to another layer or keep it as is and benefit from containers portability, live migration, vertical scaling elasticity, density and other features. Come to this session to see live migration across several clouds in action with no downtime or data loss.
originally published at TheMotion.com blogIn recent months, several colleagues asked me why I started working at TheMotion if I was already employed with one of the best development and product teams in the country: development practices consolidated, sane culture and in continuous improvement, XP, DevOps culture, an interesting product with good quality (see Alea Soluciones Bifer team).For me, the answer was simple: to learn and improve as a professional.For some time now, I’ve had an interest...
Per automatizzare la CI e la CD, durante sviluppo, test, in preproduzione e in produzione si utilizzano le tecniche chiamate attualmente DevOps, in locale con Vagrant oppure su una PAAS su cloud, privati o pubblici. Possiamo costruire una PAAS scalabile utilizzando solo Docker, Docker e Kubernetes oppure soluzioni già pronte come Openshift 3 (che sta sopra Docker e Kubernetes). Nella presentazione vedremo come avere questi tre tipi di PAAS con in più uno strato di orchestrazione in GO/Java e Ansible per automatizzare il comportamento in base ad eventi monitorati