Beauty Is in the Eye of the Beholder
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on Jan 23, 2008
MPI or Message Passing Interface is the standard for distributed programming such as that used in supercomputers and implementations can be found for FORTRAN, C, and C++. There are several projects in the works to bring that power to .NET. Today we look at two of them.
The first is Pure Mpi.NET. This implementation is written entirely in managed code and heavily leverages the Windows Communication Foundation. It also changes the API to better match the .NET style of framework writing, leaving one to wonder if there is anything left of MPI in Pure Mpi.NET.
Pure Mpi.NET has another flaw; its licensing agreement is rather onerous. The license is only granted to non-profit organizations such as schools and individuals. For profit companies are explicitly from using the library.
The next is MPI.NET. This is an open source project based on Boost.MPI. Though currently a technology preview, the API is already well documented. In addition to not being production grade, MPI.NET is tied to Microsoft's MPI implementation, MS-MPI. This means that production systems will have to run Microsoft Compute Cluster Server 2003 at 469 USD/server.
When one looks at the sorry state of MPI support on the .NET platform, it is hard not to wonder why it has taken so long to catch up to languages like FORTRAN for distributed programming.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Catch up to FORTRAN? Are you serious? FORTRAN has been dead for a looong time. .NET is here, it's not going anywhere, and is the platform of the future. It's great for distributed systems, but lacks some things for distributed parallel programming. It doesn't have a single program / multiple data parallel model, and these implementations fill in that gap.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
1 comment
Watch Thread Reply