Skip to main content

Home/ Arquitectura?/ Group items tagged oracle

Rss Feed Group items tagged

Pablo Lalloni

Quest Data Connectors - Cloudera Support - 0 views

  •  
    "Quest Data Connector for Oracle and Hadoop is a freeware plug-in to Cloudera's Distribution including Apache Hadoop that allows for fast and scalable data transfer between Hadoop and Oracle. Attributes: Transfer data to and from Oracle up to 5 times faster than Sqoop alone. Can easily transfer data to and from Oracle that has no primary key or was not stored in primary key order. Reduces overhead on the Oracle instance: Upwards of 80% reduction in CPU consumption. Up to 95% reduction in IO time. Allows other Oracle workloads to simultaneously run seamlessly without disruption. SLA-driven commercial support available when used as a part of Cloudera Enterprise."
Pablo Lalloni

Data Connector for Oracle and Hadoop - Unstructured and Structured Data Transfers - 0 views

  •  
    "Data Connector for Oracle and Hadoop is the fastest, most scalable way to transfer data between Oracle and Hadoop. "
Pablo Lalloni

VirtualBox VMs for Developers - 0 views

  •  
    "Learning your way around a new software stack is challenging enough without having to spend multiple cycles on the install process. Instead, we have packaged such stacks into pre-built Oracle VM VirtualBox appliances that you can download, install, and experience as a single unit."
Pablo Lalloni

Neo Technology execs: How Neo4j beat Oracle Database - Neo Technology - 0 views

  •  
    jejeje
Pablo Lalloni

http://labs.oracle.com/techrep/1994/smli_tr-94-29.pdf - 0 views

  •  
    Asombroso: un paper de 1994 de investigadores de Sun en el cual concluyen que "RPC" está roto de varias maneras y que no se puede arreglar con ninguna implementación. Ummm... ¿de qué año era CORBA? ¿de qué año era EJB?
Pablo Lalloni

RDBMS Competitive Analysis - 1 views

  •  
    Comparación interesante de RDBMS (incluyendo Oracle) y particularmente la opción de NuoDB.
Pablo Lalloni

Java HotSpot VM Options - 1 views

  •  
    This document provides information on typical command-line options and environment variables that can affect the performance characteristics of the Java HotSpot Virtual Machine.
Pablo Lalloni

Java API for JSON Processing: An Introduction to JSON - 0 views

  •  
    Introducción a JSONP (Java API for JSON Processing) nacida de la JSR353.
Pablo Lalloni

Examining OpenSSO Enterprise (Sun OpenSSO Enterprise 8.0 Technical Overview) - 0 views

  •  
    "OpenSSO Enterprise Technical Overview"
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.
1 - 20 of 20
Showing 20 items per page