seeebiii

public class Constants {

    /**
     * Contains the path to your Lambda function code.
     */
    public static final String LAMBDA_TASK_ROOT = System.getenv("LAMBDA_TASK_ROOT");

    /**
     * The environment variable is set to one of the following options, depending on the runtime of the Lambda function:
     * AWS_Lambda_nodejs, AWS_Lambda_nodejs4.3, AWS_Lambda_nodejs6.10

revett

Tutum Zero Downtime Re-deploy

I tweeted Tutum last night asking if they're looking at implementing zero downtime re-deploys for a given service. Slightly surprised by their response as it seems like a critical feature if you want to use the service for a production environment.

"not a top priority, but by Spring :)"

As Tutum currently doesn't support graceful termination of containers within a service, I was experiencing a 5-10 second window of 503 errors, so decided to use the following hack (code below) until the feature is officially implemented.

arobson

Abstraction Suggestions

Summary: use good/established messaging patterns like Enterprise Integration Patterns. Don't make up your own. Don't expose transport implementation details to your application.

Broker

As much as possible, I prefer to hide Rabbit's implementation details from my application. In .Net we have a Broker abstraction that can communicate through a lot of different transports (rabbit just happens to be our preferred one). The broker allows us to expose a very simple API which is basically:

• publish
• request
• start/stop subscription

dkleehammer

define([
    'marionette',
    'router',
    'controller',
    'modules/auth',
    'modules/vent',
    'views/_layout'
], function(Marionette, Router, Controller, Auth, Vent, Layout){
    var App = new Marionette.Application();

webgio

App = new Marionette.Application();

App.addRegions {
  "headerRegion": "#header"
  "topMenuRegion": "#top-menu"
  "mainRegion"  : "#main"
  }

App.on 'initialize:after', ->
  Backbone.history.start()

clarle

Next-generation JavaScript frameworks

Web application frameworks have been developing fast in the past few years, and as the technologies that they're built on top of get more advanced, each of these frameworks is able to provide newer features to help developers build more complex applications. This year, we've seen the release of a new class of application frameworks that takes advantage of JavaScript's ability to be both on the client and the server. What this allows these frameworks to do is provide both a new level of abstraction by sharing code between client and server, as well as embrace the benefits of both client-side rendering and server-side rendering.

For the end user, they get smooth, desktop-like responsiveness from client-side rendering, while still being able to maintain the SEO and accessbility benefits of server-side rendering. For developers, that means writing less boilerplate code, and being able to focus more on writing the application logic.

Today, there are three main framew

coolaj86

Getting Started with NPM (as a developer)

As easy as 1, 2, 3!

Updated:

• Aug, 08, 2022 update config docs for npm 8+
• Jul 27, 2021 add private scopes
• Jul 22, 2021 add dist tags
• Jun 20, 2021 update for --access=public
• Sep 07, 2020 update docs for npm version

domenic

//////////////////////////
// Pure "DI style" modules

// BackEndAnalytics.js
define(function () {
    return function BackEndAnalytics() {
        this.send = function () { };
    };
});