Skip to main content

Home/ Arquitectura?/ Group items tagged frameworks

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
munyeco

frameworks for developers. una novedad es spring! - 1 views

devzum.com

shared by munyeco on 15 Oct 14 - No Cached
  • Pablo Lalloni on 16 Oct 14
     
    wtf?
Pablo Lalloni

Microservices and PaaS - Part I | ActiveState - 0 views

www.activestate.com/...microservices-and-paas-part-i

development programming cloud-computing microservices architecture software-architecture software-engineering

shared by Pablo Lalloni on 25 Aug 14 - No Cached
  • 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
      Pablo Lalloni on 25 Aug 14
       
      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

jepsen-io/jepsen: A framework for distributed systems verification, with fault injection - 0 views

github.com/jepsen

development tools testing distributed-computing system-verification architecture

shared by Pablo Lalloni on 22 Dec 18 - No Cached
  • Pablo Lalloni on 22 Dec 18
     
    "Breaking distributed systems so you don't have to. Jepsen is a Clojure library. A test is a Clojure program which uses the Jepsen library to set up a distributed system, run a bunch of operations against that system, and verify that the history of those operations makes sense. Jepsen has been used to verify everything from eventually-consistent commutative databases to linearizable coordination systems to distributed task schedulers. It can also generate graphs of performance and availability, helping you characterize how a system responds to different faults. See jepsen.io for examples of the sorts of analyses you can carry out with Jepsen."
Pablo Lalloni

Angular vs. React: The Framework Way or the Library Way? | Toptal - 1 views

www.toptal.com/...r-vs-react-for-web-development

reactjs angularjs programming development javascript typescript web-development

shared by Pablo Lalloni on 27 Jun 17 - No Cached
    • Pablo Lalloni
      Pablo Lalloni on 27 Jun 17
       
      Muy buena esta comparación bien bien en la práctica. Comparación actualizada de React con Angular.
« First ‹ Previous 81 - 88 of 88
Showing 20▼ items per page