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 Jenni Konrad on Feb 16, 2012
Microsoft has announced that the upcoming Entity Framework (EF) 5 could potentially improve performance up to 67 percent over EF 4.
According to the ADO.NET team blog, the application performance improvements they've seen in this version of EF are partly due to auto-compilation of LINQ to Entities queries. The feature has always been a part of the framework, but developers had to call CompiledQuery.Compile to take advantage of it. This will now be handled automatically in EF 5: the first time a query is run, it's compiled and cached, so that successive requests can avoid the compilation step completely.
EF 4 made use of a compiled query cache for ESQL queries, and EF 5 is extending this functionality to LINQ to Entity queries. Once the cache reaches 800 compiled queries an eviction algorithm kicks in that will clean the cache periodically, once every minute. Entries are removed from the cache on a LFRU (Least frequently – recently used) basis.
Performance also improves using compiled LINQ to SQL queries. The ADO.NET team notes some changes to the way that query parameters are evaluated, which has resulted in up to 600 percent performance improvements in their internal testing.
Despite efforts to deliver .NET Framework and EF releases independent of one another, the frameworks still share some core libraries: System.Data.Entity.dll, System.Data.Entity.Design.dll, and System.Web.Entity.dll. The upside to this fact is that developers using EF 4.0 should also experience performance improvements just by upgrading to .NET Framework 4.5.
Because some of the new features in EF 5, such as Enum support and Spatial datatypes, are dependent on functionality in .NET Framework 4.5, it is not expected until after .NET 4.5 is released. Microsoft announced the availability of EF 4.3 earlier this month.
Automating Error Reporting for .NET Applications
Introducing SQLFire: a memory-optimized, high performance SQL database
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
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