Skip to main content

Home/ Arquitectura?/ Group items tagged message-processing

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Pablo Lalloni

NSQ: realtime distributed message processing at scale - 0 views

word.bitly.com/...nsq

development programming infrastructure messaging message-processing distributed-computing

shared by Pablo Lalloni on 06 Jul 15 - No Cached
  • Pablo Lalloni on 06 Jul 15
     
    "NSQ is a realtime message processing system designed to operate at bitly's scale, handling billions of messages per day."
Pablo Lalloni

9 Docker Recipes for Java EE Applications | Voxxed - 0 views

www.voxxed.com/...cipes-for-java-ee-applications

development cloud-computing infrastructure tools operations docker devops

shared by Pablo Lalloni on 15 Mar 15 - No Cached
  • Pablo Lalloni on 15 Mar 15
     
    "A typical Java EE application consists of an application server, such as WildFly, and a database, such as MySQL. In addition, you might have a separate front-end tier, say Apache, for load balancing a number of application server. A caching layer, such as Infinispan, may be used to improve overall application performance. Messaging system, such as ActiveMQ, may be used for processing queues. Both the caching and messaging components could be setup as a cluster for further scalability. This Tech Tip will show some simple Docker recipes to configure your containers that use application server and database. Subsequent blog will cover more advanced recipes that will include front-end, caching, messaging, and clustering. "
Pablo Lalloni

Nux - Overview - 0 views

acs.lbl.gov/nux

xml xom programming development jvm stax xpath xquery jaxb streaming

shared by Pablo Lalloni on 30 Mar 12 - Cached
  • Pablo Lalloni on 30 Mar 12
     
    Nux is an open-source Java toolkit making efficient and powerful XML processing easy. It is geared towards embedded use in high-throughput XML messaging middleware such as large-scale Peer-to-Peer infrastructures, message queues, publish-subscribe and matchmaking systems for Blogs/newsfeeds, text chat, data acquisition and distribution systems, application level routers, firewalls, classifiers, etc.
Pablo Lalloni

Hama - a general BSP framework on top of Hadoop - 0 views

hama.apache.org

development programming bsp hadoop cloud-computing distributed-computing bigdata big-data

shared by Pablo Lalloni on 05 Aug 13 - No Cached
  • Pablo Lalloni on 05 Aug 13
     
    "Apache Hama is a pure BSP (Bulk Synchronous Parallel) computing framework on top of HDFS (Hadoop Distributed File System) for massive scientific computations such as matrix, graph and network algorithms. Today, many practical data processing applications require a more flexible programming abstraction model that is compatible to run on highly scalable and massive data systems (e.g., HDFS, HBase, etc). A message passing paradigm beyond Map-Reduce framework would increase its flexibility in its communication capability. Bulk Synchronous Parallel (BSP) model fills the bill appropriately. Some of its significant advantages over MapReduce and MPI are: * Supports message passing paradigm style of application development * Provides a flexible, simple, and easy-to-use small APIs * Enables to perform better than MPI for communication-intensive applications * Guarantees impossibility of deadlocks or collisions in the communication mechanisms"
Pablo Lalloni

Typesafe boosts Heluna Anti-Spam Service - 0 views

typesafe.com/...luna%20Case%20Study%20v1.0.pdf

programming scala library development case-study success-stories akka play! typesafe architecture infrastructure

shared by Pablo Lalloni on 04 Mar 13 - No Cached
  • Pablo Lalloni on 04 Mar 13
     
    "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

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.
munyeco

Opensso *INACTIVE PROJECT*: users@opensso.java.net: Archive - Project Kenai - 0 views

java.net/...134

shared by munyeco on 09 Jul 15 - No Cached
  • munyeco on 09 Jul 15
     
    Hello everybody, I'm developing a custom authentication module. As part of the process I have to redirect the user to a second site and then the second site redirect the user back to the custom module. For this I'm using the RedirectCallback, but while debugging I noticed that the module gets initialized a second time after the users comes back from the second site. I was wondering if this is the expected behavior or if I'm doing something wrong. This is how the callbacks are defined in the xml.
1 - 8 of 8
Showing 20▼ items per page