Skip to main content

Home/ Arquitectura?/ Group items tagged microservices

Rss Feed Group items tagged

Pablo Lalloni

Microservices and PaaS - Part I | ActiveState - 0 views

  • Instead of building software that resembles our existing organizations, we should figure out how we want our software to look, then build the organization around that. Or reorganize it if it's already in place.
    • Pablo Lalloni
       
      Las implicancias de esta idea en nuestra organización...
  • When deploying a new feature, enhancing or fixing an existing capability, or deploying an experimental line of code, the previous code remains available and accessible. New code is deployed alongside the old code, with mechanisms in place to instantly route to one or another version.
  • Importantly, the old code is not replaced, but remains part of the system, and is kept running. If, as is often the case, the widespread introduction of the new feature results in unforeseen consequences, the feature flag can be toggled off, and the old version is instantly used instead.
  • ...13 more annotations...
  • In a microservices architecture, an application is comprised of a number of small, independent composable services that interact by way of an external published protocol, such as REST, or a messaging service.
  • Each service is focused on an individual targeted business capability, and thus its scope is minimized. For functionality out of scope, the microservice calls out to other microservices via the published protocol.
  • Small independent microservices can be built using the technology best suited for their requirements. No longer does every application component need to be built on a common company-mandated language and framework such as Java/Spring or Ruby on Rails.
  • Similarly, there's no reason to standardize on a single persistence layer across an entire application. Some microservices might best be served by Redis, others by Oracle.
  • Each microservice can be updated independently, no longer requiring the entire application to be redeployed.
  • Microservices drastically improve the time required to push out a new update, allowing a much more agile development process.
  • Many organizations consist of specialized silo teams (UI, database, API, etc) where costly handoffs and intercommunication are required to coordinate all the pieces of application construction. These handoffs cause overhead, and the need for them should be eliminated.
  • With small teams, each focused on an individual microservice, Netflix enables developers to push code to production, instead of getting mired in a complex deployment process involving several teams.
  • With microservices, the old IT mindset just doesn't work.
  • A centralized IT department cannot possibly cover the wide array of technologies spanning all microservices.
  • Instead a DevOps structure, where each team is responsible for the management of the corresponding microservice, is essential.
  • Enable developers to concoct systems of their choosing with minimal or no interaction from IT, management, VPs, hardware or other groups. "Self Service" is one of the major capabilities offered by the cloud and there's every reason to take advantage of this.
  • Now, IT can be considered as a cloud API available to the developer on-demand 24x7, instead of a complex, process-mired division hidden behind obscure process.
Pablo Lalloni

Microservices Tips and Tricks - 1 views

  •  
    "Microservices based architectures are not new but are suddenly in the spotlight due to their powerful and sophisticated practices enabling streamlined application development and deployment. However, transitioning from a monolithic approach to a microservices-based architecture requires not only technical expertise, but organizational buy-in as well. In a recent ActiveState webinar, John Wetherill and Phil Whelan discussed a number of tips and tricks to help companies transition to and get the most out a microservices-based approach."
Pablo Lalloni

Building microservices with Scala, functional domain models and Spring Boot - 0 views

    • Pablo Lalloni
       
      Muy buenos slides que muestran un posible modelo a adoptar para arquitectura de microservicios basados en event-sourcing. Imperdible. 
  •  
    "In this talk you will learn about a modern way of designing applications that's very different from the traditional approach of building monolithic applications that persist mutable domain objects in a relational database.We will talk about the microservice architecture, it's benefits and drawbacks and how Spring Boot can help. You will learn about implementing business logic using functional, immutable domain models written in Scala. We will describe event sourcing and how it's an extremely useful persistence mechanism for persisting functional domain objects in a microservices architecture."
Pablo Lalloni

Microservices and PaaS - Part II | ActiveState - 0 views

  • All aspects of deployment, monitoring, testing, and recovery must be fully automated.
  • Refactor database schemas, and de-normalize everything, to allow complete separation and partitioning of data.
  • There should be no sharing of underlying tables that span multiple microservices, and no sharing of data. Instead, if several services need access to the same data, it should be shared via a service API (such as a published REST or a message service interface).
    • Pablo Lalloni
       
      Aleluya!
  • ...5 more annotations...
  • Instead each microservice should have its own scm repository so it can truly be updated and enhanced independent of other services.
  • Gone are the days of a single monolithic database instance that's shared across all parts of an application.
  • Each microservice must have its own manifest and dependencies, instead of maintaining a global dependency list for all services.
  • Containerization brings countless advantages, particularly a consistent, isolated runtime environment that can easily migrate around the datacenter or around the globe. With Docker and other modern containerization approaches, there is very little overhead in running in a container, and considerable upside.
  • Do not build stateful services. Instead, maintain state in a dedicated persistence service, or elsewhere.
Pablo Lalloni

Kong: Next-Generation API platform for Microservices - 0 views

  •  
    "Quickly build API-centric applications. Leverage the latest microservice and container design patterns. And tie it all together with the Kong microservice API gateway."
Pablo Lalloni

Microservices and PaaS - Part III | ActiveState - 1 views

  •  
    "The Challenges of Microservices"
Pablo Lalloni

Building Applications with Microservices and Docker - NGINX - 0 views

  •  
    Why a transition to microservices and cloud development is necessary and why monolithic architectures aren't an option anymore. How to implement Docker in a cloud and continuously integrated environment and what the typical Docker-run applications look like. How NGINX and NGINX Plus can help support your migration to the modern way of building, deploying, and scaling applications.
Pablo Lalloni

https://info.typesafe.com/rs/558-NCX-702/images/COLL-white-paper-microservices-conductr... - 1 views

  •  
    "Microservices in Production"
Pablo Lalloni

Go Microservices with Go kit: Introduction - Shiju Varghese - Medium - 0 views

  •  
    "Go Microservices with Go kit: Introduction"
Pablo Lalloni

Istio and the Future of Service Meshes - 0 views

  •  
    "The microservices architectural style simplifies implementing individual services. However, connecting, monitoring and securing hundreds or even thousands of microservices is not simple.A service mesh provides a transparent and language-independent way to flexibly and easily automate networking, security, and observation functions. In essence, it decouples development and operations for services.The Istio service mesh is split into 1) a data plane built from Envoy proxies that intercepts traffic and controls communication between services, and 2) a control plane that supports services at runtime by providing policy enforcement, telemetry collection, and certificate rotation.The near-term goal is to launch Istio to 1.0, when the key features will all be in beta (including support for Hybrid environments)The long-term vision is to make Istio ambient."
munyeco

Microservices and PaaS - Part IV | ActiveState - 0 views

  •  
    Un capítulo mas de Microservices y Paas. La Quinta edición, vespertina. Ampliaremos
Pablo Lalloni

Docker Buenos Aires - microservices using relocatable docker containe… - 1 views

  •  
    "Docker Buenos Aires - microservices using relocatable docker containers"
Pablo Lalloni

istio/istio: An open platform to connect, manage, and secure microservices. - 0 views

  •  
    "An open platform to connect, manage, and secure microservices."
Pablo Lalloni

Kubernetes-native microservices API Gateway: Ambassador - 1 views

  •  
    "KUBERNETES-NATIVE API GATEWAY FOR MICROSERVICES BUILT ON THE ENVOY PROXY"
Pablo Lalloni

restQL - microservice query language - 0 views

  •  
    "restQL is a microservice query language that makes easy to fetch information from multiple services in the most efficient manner."
Pablo Lalloni

Kong - API Management and Microservice Management - 0 views

  •  
    "Secure, Manage & Extend your APIs and Microservices The open-source management layer for APIs, delivering high performance and reliability."
Pablo Lalloni

linkerd - 1 views

  •  
    "Industrial strength RPC proxy for microservices"
1 - 20 of 61 Next › Last »
Showing 20 items per page