Skip to main content


Showing posts from September, 2013

Dynamic configurations on remote clients

Strategy 1:Use server to provide configuration:

Every client will have to use this configuration.
No per client configuration option.
Requires setting jvm params

Strategy 2: Send configuration file to client on default location.

Per client configuration possible
Strategy requires transmitting file to client.
Requires setting jvm params

Strategy 3: Build client handler looking for flags.

Per client configuration possible
Strategy requires building handler.
Not easy to add features later on.
Doesn't require jvm params

Key design rights:

Passing bits to individual client is key rather server side
Use the build-in logback handler is better rather building one.

passing logger:level is the possible, handler will look if logger are set and will use if found.
handler will reset all previous configuration.

Best solution: Key is pass the file.

This will be future proof
Works per client
Requires setting jvm params

Logback know how-to

What is logback? Logback is intended as a successor to the popular log4j project. It was designed by Ceki Gülcü, log4j's founder. 

package chapters.introduction;import org.slf4j.Logger;import org.slf4j.LoggerFactory;publicclassHelloWorld1{publicstaticvoid main(String[] args){Logger logger =LoggerFactory.getLogger("chapters.introduction.HelloWorld1");     logger.debug("Hello world.");}}
Logger, Appenders and Layouts Logback is built upon three main classes: Logger, Appender and Layout. These three types of components work together to enable developers to log messages according to message type and level, and to control at runtime how these messages are formatted and where they are reported. The Logger class is part of the logback-classic module. On the other hand, the Appender and Layout interfaces are part of logback-core. As a general-purpose module, logback-core has no notion of loggers.

Logger context The first and foremost advantage of any logging API over p…


Raspberry PI won at VMware Borathon 2 day event

Idea: Cloud automation through Twitter integration.

Manage entire app lifecycle, deploy, destroy, scale-out & scale-in via Tweets from anywhere anytime.

Manage complex apps like Hadoop cluster,  JEE Cluster, Drupal, High performance DB's (Oracle etc).