Skip to main content

Home/ Arquitectura?/ Group items tagged update

Rss Feed Group items tagged

Pablo Lalloni

inconshreveable/go-update: Build self-updating Golang programs - 0 views

  •  
    "Build self-updating Golang programs"
Pablo Lalloni

rhysd/go-github-selfupdate: Binary self-update mechanism for Go commands using GitHub - 0 views

  •  
    "go-github-selfupdate is a Go library to provide self-update mechanism to command line tools."
Pablo Lalloni

robbyrussell/oh-my-zsh - 0 views

  •  
    A community-driven framework for managing your zsh configuration. Includes 40+ optional plugins (rails, git, OSX, hub, capistrano, brew, ant, macports, etc), over 80 terminal themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
  •  
    Excelentes configuraciones de prompt y auto-completar para trabajo con git y git-flow!
Pablo Lalloni

lihaoyi/scala.rx · GitHub - 0 views

  •  
    "Scala.Rx is an experimental change propagation library for Scala. Scala.Rx gives you Reactive variables (Rxs), which are smart variables who auto-update themselves when the values they depend on change. The underlying implementation is push-based FRP based on the ideas in Deprecating the Observer Pattern."
Pablo Lalloni

Field-Level Declarative Security « The Isomorphic Software Blog - 0 views

  •  
    En SCT, luego de muchos intentos, renunciamos a implementar algo así... y acá está hecho. Excelente: This allows restriction of access privileges by role to ensure granular security at a per-field level. View, search, initialize or update DataSource fields requiring specific roles with automatic consequences in the UI.
Pablo Lalloni

Eclipse Gemini Blueprint - Home - 0 views

  •  
    Gemini Blueprint project makes it easy to build Java applications that run in an OSGi framework. By using Gemini Blueprint, applications benefit from using a better separation of modules, the ability to dynamically add, remove, and update modules in a running system, the ability to deploy multiple versions of a module simultaneously (and have clients automatically bind to the appropriate one), and a dynamic service model.
Pablo Lalloni

Slick 2.0.0 - 0 views

  •  
    "These are the major new features added since Slick 1.0.1: A code generator that reverse-engineers the database schema and generates all code required for working with Slick. New driver architecture to allow support for non-SQL, non-JDBC databases. Table definitions in the Lifted Embedding use a new syntax which is slightly more verbose but also more robust and logical, avoiding several pitfalls from earlier versions. Table definitions (and their * projections) are not restricted to flat tuples of columns anymore. They can use any type that would be valid as the return type of a Query. The old projection concatenation methods ~ and ~: are still supported but not imported by default. In addition to Scala tuples, Slick supports its own HList abstraction for records of arbitrary size. You can also add support for your own record types with only a few lines of code. All record types can be used everywhere (including table definitions and mapped projections) and they can be mixed and nested arbitrarily. Soft inserts are now the default, i.e. AutoInc columns are automatically skipped when inserting with +=, ++=, insert and insertAll. This means that you no longer need separate projections (without the primary key) for inserts. There are separate methods forceInsert and forceInsertAll in JdbcProfile for the old behavior. A new model for pre-compiled queries replaces the old QueryTemplate abstraction. Any query (both, actual collection-valued Query objects and scalar queries) or function from Column types to such a query can now be lifted into a Compiled wrapper. Lifted functions can be applied (without having to recompile the query), and you can use both monadic composition of Compiled values or just get the underlying query and use that for further composition. Pre-compiled queries can now be used for update and delete operations in addition to querying. threadLocalSession has been renamed to dynamicSession and the corresponding methods have distinct names (e.g. w
Pablo Lalloni

Metascraper - 0 views

  •  
    "A Scala Library for Scraping Page Metadata. Scraping metadata (e.g. title, description, url, etc.) from a URL is something that Facebook currently does for you when you paste a URL into the "Update Status" box. For a service that I'm currently building out, we wanted to do this as well for our users. Thus Metascraper was born. There was already a Ruby solution called link_thumbnailer, but since this is a I/O heavy operation, I knew I wanted to build a solution using tools that supported non-blocking I/O and could be used without getting caught in callback spaghetti. Scala, Akka, and the Play framework immediately came to mind."
Chancha Mazzoni

How to scale Docker containers in production - 3 views

  •  
    Distintos framework/herramientas de docker en el mundo de cloud IaaS/PaaS comentando las nuevas herramientas que fueron surjiendo con Update1 Update2 etc
Sebastián Zaffarano

http://domino.research.ibm.com/library/cyberdig.nsf/papers/0929052195DD819C85257D230068... - 2 views

  •  
    An Updated Performance Comparison of Virtual Machines and Linux Containers
  •  
    Muy buena data!
Pablo Lalloni

May 15, 2014 | Typesafe Activator - An Update and Roadmap Preview | Typesafe - 0 views

  •  
    Novedades importantes de Activator, para usuarios y desarrolladores de sbt, play y akka.
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

All about Apache Aurora | Twitter Blogs - 1 views

  •  
    "What is Aurora? Platforms like Twitter operate across tens of thousands of machines, with hundreds of engineers deploying software daily. In this type of environment, automation is critical. Aurora is software that keeps services running in the face of many types of failure, and provides engineers a convenient, automated way to create and update these services. To accomplish this, Aurora leverages the Apache Mesos cluster manager, which provides information about the state of the cluster. Aurora uses that knowledge to make scheduling decisions. For example, when a machine experiences failure Aurora automatically reschedules those previously-running services onto a healthy machine in order to keep them running."
Pablo Lalloni

The Top 10 Javascript MVC Frameworks Reviewed - CodeBrief - 1 views

    • Pablo Lalloni
       
      Estos features me parecen que son excelentes objetivos a buscar.
  • Specifically, the following four features are very important to me: UI Bindings - I’m not just talking about templates, I’m talking about a declarative approach to automatically updating the view layer when the underlying model changes. Once you have used a framework (such as Flex) that supports UI bindings, you can never go back. Composed Views - Like all software developers, I enjoy creating modular reusable code. For this reason, when programming UI, I would like to be able to compose views (preferably at the template layer). This should also entail the potential for a rich view component hierarchy. An example of this would be a reusable pagination widget. Web Presentation Layer - We are programming for the web here people, the last thing I want are native-style widgets. There is also no reason for a web framework to create it’s own layout manager. HTML and CSS are already the richest way to do style and layout in existence, and should be used as such. The framework should be centered around this concept. Plays Nicely With Others - Let’s face it, jQuery is pretty amazing. I don’t want a framework which comes bundled with a sub-par jQuery clone, I want a framework which recommends using jQuery itself.
    • Pablo Lalloni
       
      ESTOS features
munyeco

Service Discovery & Orchestration With Mesos and Consul | My Tech Musings and Stuff I W... - 4 views

  • Joel, we chose consul for a few reasons. First, I wanted a service discovery solution that could work with our legacy architectures as well as any new projects we run on mesos. In addition, I wanted a way to bootstrap the mesos cluster setup/configuration (masters and slaves) such that when they are provisioned, they will be auto-configured using data in consul. Think zk values, quorum, etc. I’ll be working on a solution for this very soon. Lastly, I really like how consul supports health-checks, which we will leverage heavily to ensure that only “healthy” services are actually registered. Like you mentioned, consul is very fast in updating the service info and that is very important as well. Hope that helps, -Phil
1 - 20 of 21 Next ›
Showing 20 items per page