Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Bienvenido David III on Aug 18, 2011
ej-technologies GmbH has released JProfiler 7.0. JProfiler is a Java SE/EE profiling tool which features CPU profiling, memory profiling, thread profiling and VM telemetry. The new features for version 7.0 are:
JProfiler now has built-in probes for JDBC, JMS, JNDI, Servlets, files, sockets and processes, which records and analyzes data from various subsystems. Probes have a timeline view for long-lived objects. For example, database connections are displayed in a timeline which shows when they are idle, when they running a statement, or when they are running a batch transaction. Probes also have an events view, which shows events with thread and stack trace information. For example, the JDBC probe will display events like connecting to databases or running queries. Probes also have an objects view for details and statistics, a hot spot view that shows the most expensive methods calls, and a telemetries view that graphically displays the telemetries published by the probe. These built-in probes can be configured in the JProfiler session settings.
JProfiler also supports the creation of custom probes. It offers an API for developing a custom probe and deploying it together with the profiled application. JProfiler also offers a custom probe wizard that allows you to define your custom probes within the JProfiler GUI. You specify which methods in your application you want to intercept and create "interception scripts" that are called with the help of the JProfiler code editor. Custom probes can be added or changed without the need to restart the profiled application. Note that a run script trigger has also been added in this release, which is a way to execute code when a certain method is called, and thus an alternative to simple custom probes.
JProfiler also introduces the concept of request tracking, which makes profiling of parallel and multi-threaded applications easier. Request tracking connects call sites with execution sites between different threads in the call tree view. For example, you can use this feature to know how much time was spent to complete an asynchronous task or find the origin of an asynchronous task. Executors, Thread starts, and AWT/SWT events can all be tracked using request tracking.
A couple of enhancements have also been made on JProfiler heap walker.
Standard license pricing starts at US$499 per developer. A 10 day trial is also available. If you own an older copy of JProfiler with support, you can upgrade your old license key for free. If you no longer have support, you will need to purchase an upgrade.
An open source alternative to JProfiler is Java VisualVM. Some commercial alternatives include YourKit and JProbe.
For more details about the new JProfiler 7.0, visit the JProfiler what's new and changelog pages.
Introducing SQLFire: a memory-optimized, high performance SQL database
RDBMS to NoSQL: Managing the Transition
Combining Inspections, Static Analysis, Testing to Achieve >95% Defect Removal Efficiency
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply