rest

La tercera edición de esta saga de buenos propósitos. Dentro de poco enviaré el boletín dominical número 100. Me encantaría que lo recibieras en tu bandeja de entrada. Suscríbete gratis. Después de Lo que me gustaría aprender en 2019 y 2018 va el de este año. La conclusión de la última edición es que se ha conseguido en parte: si he mejorado en cuanto a frameworks de JavaScript y despliegues en la nube. Pero no he avanzado de forma significativa en machine learning. Para este año el menú es...

This past 17th of November, we celebrated at Nextail's offices in Madrid, the second TejonesConf. This "unconference" that started as an inside joke (See TejonesConf 2018) has become a great event to share, to learn, and to enjoy with friends. The "unofficial" motto for this edition was "agility and product development, from experience and without smoke or shit." :)In this case, I was very involved in the organization, so in addition to trying to share in the sessions, I also tried to be aw...

Cuando pensamos en un API, pensamos automáticamente en REST, salvo que te hayas quedado viviendo en 1999 y pienses en SOAP. En 2012 Facebook comienza el desarrollo GraphQL y en 2015 hace público https://graphql.org donde describe formalmente esta nueva forma de crear y utilizar APIs. Me gustaría enseñaros su potencia, qué ofrece en comparación con REST y hacer una pequeña demo en Ruby on Rails utilizando la gema ‘graphql-ruby’ https://github.com/rmosolgo/graphql-ruby Ponente: Daniel de la Mata

Mediante tecnologías opensource y basándonos en estándares Ethereum, desarrollaremos una criptomoneda con funcionalidades básicas expuestas mediante un API REST. De esta forma, podremos distribuir las criptomonedas entre los empleados y emplear técnicas de gamificación para la realización de cursos, recompensa a compañeros, etc Esta criptomoneda también podrá ser intercambiada posteriormente por objetos físicos La charla mostrará el proceso de creación y gestión de esta criptomoneda así como sus posibilidades a través de técnicas de gamificación About: Angel Miguel Martinez Pulido, Blockchain Architect - atSistemas Definición de arquitecturas técnicas en proyectos blockchain. Participación en propuestas y preventas en proyectos de ámbito blockchain. Generación de contenidos técnicos sobre blockchain. Arquitectura de Soluciones con Blockchain Ethereum / Quorum / Alastria / Smart Contracts usando Java, Go, NodeJS y AWS en diversos proyectos nacionales e internacionales Experiencia en tecnologías de la información en los campos de banca, seguros y sanidad

Pablo Postigo es ingeniero informático, CEO y co-fundador de Frontity y viene a contarnos para qué sirve y cuál es la historia de la creación de esta herramienta. Además de esta estupenda entrevista recuerda que sólo para los suscriptores Premium está disponible la versión "En Privado" Allí Pablo nos habla de cómo gestionan los proyectos, las herramientas de organización que usan y cómo es el perfil profesional ideal para trabajar en Frontity. Cuando quieras puedes escuchar la versión "En Pr...

Introduction. Lately, I’ve been playing a bit with property-based testing. I practised doing the FizzBuzz kata in Clojure and used the following constraints for fun[1]: Add one property at a time before writing the code to make the property hold. Make the failing test pass before writing a new property. The kata step by step. To create the properties, I partitioned the first 100 integers according to how they are transformed by the code. This was very easy using two of the operations on set...

Introduction. Recently in the B2B team at LIFULL Connect, we improved the validation of the clicks our API receive using a service that detects whether the clicks were made by a bot or a human being. So we used TDD to add this new validation to the previously existing validation that checked if the click contained all mandatory information. This was the resulting code: and these were its tests: The problem with these tests is that they know too much. They are coupled to many implementation de...

The founder of Netty introduces a new microservice framework ‘Armeria’. It is unique because it 1) has Netty-based high-perf HTTP/2 implementation, 2) lets you run gRPC, Thrift, REST, even Servlet webapp on single TCP port in single JVM, and 3) integrates with Spring Webflux and Reactive Streams. Armeria is a Netty-based open-source Java microservice framework which provides an HTTP/2 client and server implementation. It is different from any other RPC frameworks in that it supports both gRPC and Thrift. It also supports RESTful services based on Reactive Streams API and even a legacy web applications that run on Tomcat or Jetty, allowing you to mix and match different technologies into a service which means you do not need to launch multiple JVMs or open multiple TCP/IP ports just because you have to support multiple protocols or migrate from one to another. In this session, Trustin Lee, the founder of Netty project and Armeria, shows: What Armeria is. How to serve gRPC, Thrift and RESTful services on a single TCP/IP port and a single JVM. How to make your legacy Tomcat or Jetty-based application and modern reactive RPC service coexist. How to use Armeria’s universal decorator API to apply common functionalities such as circuit breaker, DNS-based service discovery, distributed tracing and automatic retry, regardless of the protocol, which was previously impossible with other RPC frameworks which focused on a single protocol.

The world is moving from a model where data sits at rest, waiting for people to make requests of it, to where data is constantly moving and streams of data flow to and from devices with or without human interaction. Decisions need to be made based on these streams of data in real-time, models need to be updated, and intelligence needs to be gathered. In this context, our old-fashioned approach of CRUD REST APIs serving CRUD database calls just doesn't cut it. It's time we moved to a stream-centric view of the world.

Are you doing microservices? Got exhausted of slow REST? Got mad of unreliable gRPC? An answer is RSocket. RSocket in a new network protocol with reactive streams semantic. It will make your system super fast and resilient. Come and learn why RSocket is the future of any cross-services communication The new generation of cross-service communication is coming and called RSocket. RSocket is a new protocol that embracing Reactive Streams semantic into cross-service messaging. This protocol enables backpressure-control and allows building canonical Reactive-System. Even though the protocol offers asynchronous messages’ streaming, there have already been a few competitors in this area by that time. One of those competitors is well-known gRPC. In this session, we are going to learn why RSocket is innovation solution for cross-server communication, can we compare it with gRPC at all and if can, what are the key differences between RSocket and gRPC and why we have to start using RSocket today.