Skip to main content

Home/ Arquitectura?/ Group items tagged cases

Rss Feed Group items tagged

Pablo Lalloni

Arquillian - 1 views

  •  
    Arquillian brings the test to the runtime so you don't have to manage the runtime from the test (or the build). Arquillian eliminates this burden by covering all aspects of test execution, which includes: Managing the lifecycle of the container (or containers) Bundling the test case, dependent classes and resources into a ShrinkWrap archive (or archives) Deploying the archive (or archives) to the container (or containers) Enriching the test case by providing dependency injection and other declarative services Executing the tests inside (or against) the container Capturing the results and returning them to the test runner for reporting
Pablo Lalloni

Case Studies & Stories | Typesafe - 0 views

  •  
    "Organizations across all industries, of all sizes are using the Typesafe Reactive Platform in amazing ways. Read through our case studies with some of the world's most innovative enterprises and startups."
Pablo Lalloni

nathanmarz/cascalog · GitHub - 0 views

  •  
    "Cascalog is a fully-featured data processing and querying library for Clojure or Java. The main use cases for Cascalog are processing "Big Data" on top of Hadoop or doing analysis on your local computer. Cascalog is a replacement for tools like Pig, Hive, and Cascading and operates at a significantly higher level of abstraction than those tools."
Pablo Lalloni

non/spire · GitHub - 0 views

  •  
    Spire is a numeric library for Scala which is intended to be generic, fast, and precise. Using features such as specialization, macros, type classes, and implicits, Spire works hard to defy conventional wisdom around performance and precision trade-offs. A major goal is to allow developers to write efficient numeric code without having to "bake in" particular numeric representations. In most cases, generic implementations using Spire's specialized type classes perform identically to corresponding direct implementations.
Pablo Lalloni

longevity - 1 views

  •  
    "Model your domain in the language and style of Domain Driven Design. Implement it using Scala case classes and companion objects. Pass us your subdomain, and we provide the persistence. Persistence concerns, operations and data are abstracted behind an elegant persistence API. We provide you with fully featured repositories for MongoDB and Cassandra. We provide a suite of integration tests to exercise your repositories against a real database, as well as in-memory repositories for other tests."
Pablo Lalloni

Scala Puzzlers - 0 views

  •  
    "Welcome to Scala Puzzlers, the collection of Traps, Pitfalls and Corner Cases in the Scala language. Prepare to be surprised, entertained and...well, puzzled! What is presented here is a selection of seemingly simple examples which demonstrate that there's plenty of head-scratching left in Scala. Let your mind be challenged by unexpected and unintuitive behaviour and results and learn something in the process. "
Pablo Lalloni

Running Secured Docker Registry 2.0 - Container Solutions - 0 views

  •  
    "The new Docker Registry 2.0 was released on April 16th, 2015. It was completely rewritten in Go with added support for the new Docker Registry HTTP API V2 (thus only working with Docker 1.6+), promising to provide faster and more secure distribution of images. If you work with Docker and for some reason decided not to use the public Docker Hub, a private Docker Registry is an essential part of your architecture. But even if you don't have private images, you will likely need to use your own registry in production/testing for efficiency. The default installation, however, runs without encryption and authentication. I was wondering what's involved in securing it. There is an official tutorial on how to configure TLS on a registry server. TLS/SSL is absolutely necessary for any secure setup, but I also wanted to enable an authentication mechanism. The Configuration Reference document describes two authentication options supported by Docker Registry itself: so-called silly and token solutions. The silly one is apparently only useful for very limited development use-cases. The token solution seems to be more serious, but because of the lack of documentation (at the time of writing), I decided to find an alternative approach to secure it. In this article I'm going to show you how to set up the Docker Registry 2.0 with username/password authentication and SSL using the official Docker Registry image and a custom configured nginx as a proxy server."
Pablo Lalloni

Colossus - 0 views

  •  
    "Colossus is a lightweight framework for building high-performance applications in Scala that require non-blocking network I/O. In particular Colossus is focused on low-latency stateless microservices where often the service is little more than an abstraction over a database and/or cache. For this use case, Colossus aims to maximize performance while keeping the interface clean and concise."
Pablo Lalloni

Red Hat Advances Enterprise Virtualization Platform With RHEV 3.4 - 2 views

  • RHEV and Docker provide fundamentally different use cases, Herold explained.  "In fact, we see opportunities for RHEV to run the operating systems, including Atomic Hosts, that ultimately run Docker instances," he said. "Within the oVirt upstream project, we have an initial Docker integration to run Docker instances in VM containers provided by RHEV."
    • Pablo Lalloni
       
      Creo que la estrategia de integración de Docker de RH está equivocada. Siguiéndola obtienen la mitad de los beneficios de Docker (agilidad de empaquetamiento, distribución y deployment) pero dejan de lado la otra mitad (mucho mayor performance y eficiencia de un container versus una vm) que muchos competidores sí ofreceran a sus clientes, abriendo una brecha.
Pablo Lalloni

Typesafe boosts Heluna Anti-Spam Service - 0 views

  •  
    "Heluna offers a unique SaaS based anti-spam solution that processes millions of e-mail messages  daily. Heluna turned to the Typesafe Stack - made up of Scala, Akka and Play Framework - in order  to future-proof the platform, and allow it to easily scale out to process well into the hundreds of  millions of e-mails."
Pablo Lalloni

Google Container Registry - Tools - Google Cloud Platform - 0 views

  •  
    "Google Container Registry provides secure, private Docker image storage on Google Cloud Platform. While Docker provides a central registry to store public images, you may not want your images to be accessible to the world. In this case, you must use a private registry. The Google Container Registry runs on Google Cloud Platform, so can be relied upon for consistent uptime and security. The registry can be accessed through an HTTPS endpoint, so you can pull images from any machine, whether it's a Google Compute Engine instance or your own hardware."
Pablo Lalloni

The Journey of Go's Garbage Collector - The Go Blog - 1 views

  •  
    "The Go language features, goals, and use cases have forced us to rethink the entire garbage collection stack and have led us to a surprising place. The journey has been exhilarating. This talk describes our journey. It is a journey motivated by open source and Google's production demands. Included are side hikes into dead end box canyons where numbers guided us home. This talk will provide insight into the how and the why of our journey, where we are in 2018, and Go's preparation for the next part of the journey."
Pablo Lalloni

InfoQ: How We (Mostly) Moved from Java to Scala - 1 views

  •  
    Graham Tackley discusses how The Guardian switched all new development from Java to Scala, why they did that, what were the benefits and the problems, and why they did not choose Python+Django.
Pablo Lalloni

Informe s/ BigData en el gobierno de UK - 1 views

  •  
    "1. The Government has already made a commitment to Big Data by classifying it as one of the 'Eight Great Technologies' which will propel the UK to future growth and help it stay ahead in the global race. The 'Information Economy Strategy' reports on the increase in data being generated and the importance of new types of computing power in order to reap the economic value of the data. 2. This paper sets out to cover the following areas: a) Defining Big Data b) High-level trends in Big Data c) Opportunities for Big Data applications 3. In developing this paper, a 'community of interest' has been established comprising policy leads and analysts from across government with an interest in Big Data. This paper draws on their insights, insights from the private sector, academics, and the extensive open source literature on the Big Data topic."
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