New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Apr 23, 2010
Microsoft pattern&practices has released Enterprise Library 5.0, a set of application blocks that can be used as building blocks for enterprise applications, representing Microsoft’s guidance on how to write good applications. The library contains a number of improvements, includes Unity 2.0, and supports .NET 4.0.
Microsoft Enterprise Library 5.0 contains source code that could be used as building blocks for enterprise applications. The code can be used as provided or it can be changed or extended as needed. The main purpose of the library is to provide guidance for developers on how to write good software. The library was built using design patterns like Plug-in and Dependency Injection, the common functionality was encapsulated into the Enterprise Library Core, it uses uniform conventions for naming and versioning, all application blocks are instrumented and unit tests have been included from the initial design phase.
The Enterprise Library contains the following application blocks:
Some of the improvements of this version of the library over the previous one are:
The library can be used both on 32 and 64 bit machines but it has not been tested on Windows XP, XP not being mentioned in the list of supported operating systems. Nonetheless, Grigori Melnik does not see a reason why the library cannot be used on XP with .NET 3.5 or .NET 4.0.
Melnik also mentions that the pattern&practices team has tried to preserve compatibility with previous versions but there are some breaking changes.
Data Access: not much of ms's data accessing technologies survived long time.
Logging: enough competitors are already there and much better than this one
Unity: is really any one using it?
to be honest, a lot of things from ms are just like prince/princess. they are used only because they are under the big name. take away the name and put them in the wild, few will survive.
Mediocrity technology can survive just fine - look at Java. Mediocre companies tend to die though - Sun.
I use Unity, what's wrong with that?
I feel sad for people like you who hate MS just because they create products where other competitors/alternatives have been around for a while, and eventually MS takes a bigger market share just because they have a large customer base.
One reason why Microsoft adds frameworks/libraries that third party .NET vendors have already provided is that they have many customers who will not use such libraries unless they're provided by Microsoft. That's just the way it is.
Mediocrity technology can survive just fine - look at Java. Mediocre companies tend to die though - Sun.
If Java is a mediocre technology, why did Microsoft cloned it to make .Net?
I use configuration UI for our application. It is nice to get UI for your config files and save them to central SQL storage.
If Java is a mediocre technology, why did Microsoft cloned it to make .Net?
To make it better! :)
I'm curious as to why a library, ostensibly running on the managed .NET base would give a hoot for which OS it was on as long as the supported .NET platforms run. In this case .NET 2 and .NET 4 by the look of it.
Last time I checked, XP was still fairly popular. Nothing has come out since that makes extra money for me.
As for whether the blocks are useful - that shouldn' be based on commercial alternatives, more on what you can learn from the library itself. After all it is designed to be extended and the price appears to be right
Rob,
The library doesn't. It's whether we can claim that it runs on XP without doing a test pass.
Since the release, we've conducted an additional test pass on Windows XP SP3 and added it to the list of OSs.
See
blogs.msdn.com/agile/archive/2010/04/28/enterpr...
- Grigori
It not that Java is mediocre, it just can't keep up with Microsoft. Well, I take that back the first few releases of java where incomplete. So I guess it did suck. The only reason it did well is because of marketing. Their ads should be if you hate MS then use our product. It is old and not a very productive tool set. You need a lot of third party stuff to do things with it. Suns never spent the money they needed to to keep it current. Even book store now have their java books in the back, on sale, lower shelf while the MS books are out in front. Oracle might save Java but Oracle likes money, so expect to start paying big time at some point.
Warmonger. Holywar has begun :)
A quick update. We are working on a Silverlight Integration Pack for Enterprise Library 5.0.
You are invited to preview the backlog and vote on the features.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
12 comments
Watch Thread Reply