Skip to main content

Home/ Arquitectura?/ Group items tagged service-repository

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Pablo Lalloni

Getting Started With OpenAM - 0 views

openam.forgerock.org/...index.html

development openam security

shared by Pablo Lalloni on 15 May 15 - No Cached
  • OpenAM centralizes authentication by using a variety of authentication modules. Authentication modules connect to identity repositories that store identities and provide authentication services. The identity repositories can be implemented as LDAP directories, relational databases, RADIUS, Windows authentication, one-time password services, other standards-based access management systems and much more.
  • OpenAM centralizes authorization by letting you use OpenAM to manage access policies separate from applications and resources. Instead of building access policy into a web application, you install a policy agent with the web application to request policy decisions from OpenAM. This way you can avoid issues that could arise when developers must embed policy decisions into their applications. With OpenAM, if policy changes or an issue is found after the application is deployed, you have only to change the policy definition in OpenAM, not deploy a new version of the application. OpenAM makes the authorization decisions, and policy agents enforce the decisions on OpenAM's behalf.
  • Pablo Lalloni on 15 May 15
     
    "OpenAM centralizes authentication by using a variety of authentication modules. Authentication modules connect to identity repositories that store identities and provide authentication services. The identity repositories can be implemented as LDAP directories, relational databases, RADIUS, Windows authentication, one-time password services, other standards-based access management systems and much more."
Pablo Lalloni

InfoQ: DIY SOA: How to build your own Simple Service Repository - 1 views

www.infoq.com/...SimpleServiceRepository

soa service-repository ideas service-registry architectura

shared by Pablo Lalloni on 14 Sep 11 - No Cached
  • Pablo Lalloni on 17 Sep 11
     
    Nosotros tenemos necesidad de un repositorio de servicios, me parece que es la única manera de lograr un poco de uniformidad, claridad y exposición en cualquier esfuerzo SOA que podamos hacer en la organización. Quizás podríamos empezar un test drive de una implementación similar a lo que proponen en el artículo dado que no requiere la "elección" de un producto en particular lo cual parece ser el factor limitante en este momento "político".
Pablo Lalloni

CloudBees DEV@cloud (Jenkins as a Service) Documentation - 0 views

wiki.cloudbees.com/...BuildHive

operations cloud jenkins cloud-computing tools continuous-integration ci infrastructure

shared by Pablo Lalloni on 04 Nov 12 - No Cached
  • Pablo Lalloni on 04 Nov 12
     
    BuildHive is a part of DEV@cloud that allows the open-source communtiy to quickly set up simple continuous integration service for GitHub repositories.
Pablo Lalloni

Microservices and PaaS - Part II | ActiveState - 0 views

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

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

shared by Pablo Lalloni on 25 Aug 14 - No Cached
  • 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
      Pablo Lalloni on 25 Aug 14
       
      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.
1 - 4 of 4
Showing 20▼ items per page