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 Abel Avram on Oct 15, 2010
New Relic has released two new variants of its performance tool: RPM for .NET and RPM for PHP. RPM offers performance monitoring and analysis for web applications running on premises or in the cloud.
New Relic’s performance tool, called RPM, is a SaaS solution for companies interested in monitoring, troubleshooting, diagnosing, thread profiling, and capacity planning for their web applications deployed locally or in the cloud.
RPM has two basic components: an agent running as an application plug-in and a service hosted by New Relic’s datacenter. The agent collects performance data and sends it asynchronously once per minute via HTTP or HTTPS to the RPM service where it is stored and processed. The service does the rest of the job: data storage, aggregation, correlation, and visualization. Performance data is accessed from the browser. New Relic does not offer the choice to run the service on-premise, it runs only on their data center.
The agent collects information on the application response time, throughput, transaction time, database calls, background jobs, and other metrics. Using the agent does not require code modification.
The monitored application can be deployed in customer’s datacenter or in the cloud: Amazon, Engine Yard, Heroku, Gigaspaces, GoGrid, etc. Collected data can be visualized per application instance, per host or per cluster of hosts. RPM for Ruby on Rails has a Developer Mode, the raw performance data being saved locally and can be used by developers to test the performance of their application during development phase.
Started in 2008, New Relic offered RPM for Java and RPM for Ruby on Rails in the beginning, and now the company has announced RPM for .NET and PHP. RPM for .NET can be used to monitor the performance of the CLR, DBs, ASP.NET MVC2, WCF, external transactions. RPM for PHP is currently a beta product targeted at PHP apps having about the same capabilities as the Java or Ruby on Rails versions of the product. RPM for PHP supports the following platforms among others: Drupal, MySQL, PostgreSQL, and WordPress.
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Automating Error Reporting for .NET Applications
Troubleshoot Java/.NET performance while getting full visibility in production
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
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