Skip to main content

Home/ Arquitectura?/ Group items tagged spring

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Pablo Lalloni

camunda/camunda-bpm-spring-boot-starter: Camunda BPM bootified! - 0 views

github.com/...amunda-bpm-spring-boot-starter

camunda bpm integration spring spring-boot

shared by Pablo Lalloni on 24 Aug 17 - No Cached
  • Pablo Lalloni on 24 Aug 17
     
    "Camunda BPM spring-bootified! "
Pablo Lalloni

gwuhaolin/spring-data-rest-js: js lib for java spring data rest service,work for node.j... - 0 views

github.com/...spring-data-rest-js

javascript hal json hypermedia programming development spring

shared by Pablo Lalloni on 05 Dec 17 - No Cached
  • Pablo Lalloni on 05 Dec 17
     
    "Spring Data Rest is makes it easy to build hypermedia-driven REST web services. This lib provider useful util to play with the service in js. It's a easy to use and lightweight (2kb after min and gzip) javascript lib can run in both node.js and browser,can be work with lib like AngularJS React Vue. support Typescript."
Pablo Lalloni

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

www.slideshare.net/...domain-models-devnexus-2015key

architecture microservices development programming event-sourcing cqrs spring-boot spring nosql docker scala functional-programming

shared by Pablo Lalloni on 16 Apr 15 - No Cached
    • Pablo Lalloni
      Pablo Lalloni on 16 Apr 15
       
      Muy buenos slides que muestran un posible modelo a adoptar para arquitectura de microservicios basados en event-sourcing. Imperdible. 
  • Pablo Lalloni on 16 Apr 15
     
    "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

Hybind - Home - 0 views

lbovet.github.io/hybind

javascript hal json hypermedia programming development

shared by Pablo Lalloni on 05 Dec 17 - No Cached
  • Pablo Lalloni on 05 Dec 17
     
    "Unlike most client libraries dealing with HAL REST APIs, Hybind provides a high-level approach similar to what Object Relational Mapping (ORM) frameworks are for databases. When using Spring Data REST in the server, it is amazing how the amount of code to write is reduced to a minimum. However, a significant amount of repeated boilerplate is still required in the JavaScript client to manipulate the resources and map them to the client-side model. That's why this library exists. It enriches plain JavaScript objects with a convenient API so that performing REST requests is as easy as calling methods directly on the model objects. It is optimized for Spring Data REST, but should work with other HAL APIs following similar conventions."
Pablo Lalloni

Dead-Simple Dependency Injection - YouTube - 2 views

www.youtube.com/watch

dependency injection dependency-injection scala functional-programming development programming

shared by Pablo Lalloni on 07 Nov 12 - No Cached
  • Pablo Lalloni on 07 Nov 12
     
    Muy buena charla de Runar Bjarnasson sobre DI estilo funcional. En alguna charla lo escuché decir algo así como:   Como todos sabemos "Inversion Of Control" es solo otra forma de llamar al "pasaje de parámetros". Y eso marca el approach alternativo al "DI estilo Spring" que tomó el mundo de la programación funcional.
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.
1 - 7 of 7
Showing 20▼ items per page