Skip to main content

Home/ Arquitectura?/ Contents contributed and discussions participated by Pablo Lalloni

Contents contributed and discussions participated by Pablo Lalloni

Pablo Lalloni

Druid | What is Druid? - 1 views

  •  
    An open-source, real-time data store designed to power interactive applications at scale.
Pablo Lalloni

How to Write a Git Commit Message - 6 views

  •  
    Una simple traducción de este post podría ser nuestra largamente necesitada convención sobre cómo escribir los comentarios de commits.
Pablo Lalloni

lauris/awesome-scala - 1 views

  •  
    "A community driven list of useful Scala libraries, frameworks and software."
Pablo Lalloni

openshift-pep/openshift-pep-013-openshift-3.md at master · openshift/openshif... - 2 views

  •  
    "OpenShift 3.x System Design"
Pablo Lalloni

OpenShift v3 Platform Combines Docker, Kubernetes, Atomic and More | Openshift Blog - 0 views

  •  
    "Today the OpenShift development team announced a new public Origin repo containing initial commits for our third generation OpenShift platform. This integrates work we've been doing over the past year plus in OpenShift Origin and related projects like Docker, Kubernetes, Geard and Project Atomic - all of which will become integral components of the new OpenShift. This Origin community effort will drive the next major releases of OpenShift Online and OpenShift Enterprise 3."
Pablo Lalloni

Stackato: The Platform for the Agile Enterprise - 0 views

  •  
    "Stackato is a secure, stable, and commercially supported Platform-as-a-Service (PaaS) that is built with and on top of various open source components such as Cloud Foundry and Docker."
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

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

Netflix Open Source Software Center - 0 views

  •  
    Colección muy interesante (y bastante impresionante) de librerías y herramientas opensource publicadas por Netflix, hechas para implementar sus servicios.
Pablo Lalloni

The New Stack and Linux Foundation Survey: OpenStack and Docker are The Most Popular Op... - 0 views

  •  
    "OpenStack and Docker will continue to dominate the open source cloud discussion. But Docker may prove to gain the most as it is also breeding a diverse ecosystem of open source projects. OpenStack is primarily contained (no pun intended) to the development of its own cloud operating system. It does integrate with OpenShift, for example, but for the most part the different groups within OpenStack do the lion's share of development. Docker's influence is such that it is affecting the overall open source community. The projects that are closely tied to Docker, such as Ansible, will continue to grow as developers seek tools to use with the fast growing container technology."
Pablo Lalloni

julien-truffaut/Monocle - 0 views

  •  
    "Monocle is a Lens library, or more generally an Optics library. Optics are a set of purely functional abstractions to manipulate (get, set, modify) immutable objects. Optics compose between each other and particularly shine with nested objects."
Pablo Lalloni

IBM Techies Pit Docker, KVM Against Linux Bare Metal - 0 views

  •  
    "A bunch of techies working in IBM's systems lab in Austin, Texas ginned up a bunch of benchmark tests to show how both KVM and Docker stacked up against bare metal iron running Linux."
Pablo Lalloni

Performance Analysis of Docker on Red Hat Enterprise Linux 7 | Red Hat Developer Blog - 0 views

  •  
    "Since earlier this year, the Performance Engineering Group at Red Hat has run huge amounts of microbenchmarks, benchmarks and application workloads in Docker containers."
Pablo Lalloni

Flynn - 1 views

  •  
    "Flynn is two things: A "distribution" of components that out-of-the-box gives companies a reasonable starting point for an internal "platform" for running their applications and services. The banner for a collection of independent projects that together make up a toolkit or loose framework for building distributed systems. Flynn is both a whole and many parts, depending on what is most useful for you. The common goal is to democratize years of experience and best practices in building distributed systems. It is the software layer between operators and developers that makes both their lives easier. Unlike most PaaS's, Flynn can run stateful services as well as 12 factor apps. This includes built-in database appliances (just Postgres to start). Flynn is modular so users can easily modify, upgrade, and replace components. "
Pablo Lalloni

octohost - Simple web focused Docker based mini-PaaS server. - 0 views

  •  
    "Simple web focused Docker based mini-PaaS server."
« First ‹ Previous 641 - 660 of 1300 Next › Last »
Showing 20 items per page