Domain Driven Design – 10 Years Later

I’ve been an avid podcaster since its inception and before podcasting I would web stream my favorite radio shows like This American Life or download the files and transfer them to crappy MP3 flash player. Ah the memories of the days before the iPhone.

I finally caught up with a software engineering radio pod from May of 2015 where the topic was reflecting on Eric Evan’s classic text Domain Driven Design 10 years after its publication.  Reflecting is right. When that book came out I about to start grad school at the University of Minnesota and reading every decent text I could get my hands on. I’ve always prefered looking wide and long at the software field and was drawn to software design, product design, & user experience rather than focusing on stack specialization, russian algorithms, etc. so Eric’s book was a natural fit for me and I remember loving it and praising to all my peers.

Those were critical years in my engineering & leadership development, I was two years removed from creating a flexible ecommerce platform with my mentor and was just beginning with a few new firms around e-leasing & digital media ecommerce.

The software engineering pod brought Eric’s voice back into my head and the terms and language from the book flushed into my thoughts. It’s amazing how memory recall can be effortless when the material, even if distant, struck a chord and anchored in your thought process.

This pod covered how DDD relates to the terms of today like: CQRS, NoSQL, & event sourcing. I was struck with how the principles of DDD have been reflected in the designs of the companies, teams, and projects I’ve worked with since 2005, regardless of the tech space or stack.  I think the book provides considerations that are still very valid today. If you haven’t read the book it’s worth your time, if you have read the book then check out the pod.

Eberhard Wolff talks with Eric Evans, the founder of domain-driven design (DDD), about its impact after 10 years. DDD consists of domain-modelling patterns; it has established itself as a sound approach for designing systems with complex requirements. The show covers an introduction to DDD, how the community’s understanding of DDD has changed in the last 10 years, the often overlooked component—strategic design, how to use DDD to design microservices, and the connection between microservices and the DDD bounded context. DDD originated during the era of object orientation and relational databases; the show concludes with a look at the recent impact of functional programming and NoSQL on DDD.

 

 

 

3D Printing

One of my hobbies is too assess markets and businesses for opportunity and growth. A market that has been hot is 3-D printing. It’s not a new technology and I’m sure there were 60 minute segments on it 20 years ago. But in the past few years it’s made that leap as something available for only for manufacturers to being available for early-adopters in the consumer market.

The printers are now consumer friendly in size, price, and use. I admit, I have not researched or worked with these printers but assessing markets as a hobby doesn’t require me to. The WSJ had an article  about this very thing. So what is the market for 3-D printers? For industry it’s a no brainer, the opportunity for prototyping alone is enough to invest in this technology.

Where else is there potential? When exploring 3-D printer manufacturers there may be something there but we’ve already started to see consolidation of firms in that maturing market. And ask yourself if you like where the consumer inkjet printing market has gone? I for one do not find it compelling and am uninterested in manufacturers.

Where the real opportunity may be is in providing the designs, the directions, the code, to producing whatever widgets people want to have at the moment. One example is folks on my development team who have used their printers to make devices that allow their iPhone to rest on their monitor for stand-ups  when working remotely. The potential to provide designs, or for a design marketplace that’s modeled like Etsy may be a potential area.

They’re are downsides worth mentioning here as well and that’s waste. When these printers reach the consumer market and potential consumer scale what will be done with all these frankenstein experiements? Where will they go? Plastics are already a problem, especially in our oceans. We do have this wonderful young man making a difference there. In the meantime, if you like to tinker and design I think 3-D printing has potential. As far as for me, I’m out.

Peecho Architecture – scalability on a shoestring

Great article by the team at Peecho on their architecture, why they went cloud-based and picked Amazon, and then an overview of their architecture.
High Scalability – High Scalability – Peecho Architecture – scalability on a shoestring.

High Scalability – Web 2.0 Killed the Middleware Star

Interesting read on the use of middleware and its relevance in a web 2.0 world. The comments should drive out some good discussion on what other folks have done.

High Scalability – High Scalability – Web 2.0 Killed the Middleware Star.

Clean flow diagram to describe the process

Today I found myself organizing and that included going through a stack of articles that were in my blog material pile. So even though I do not blog consistently, effectively, and nor do I ever put the amount of time to write a decent post I can take a small victory in the fact that I have a blog material pile. Ah, the intention and focus I have until something else comes along!

So on 10/12/10 the WSJ had an article on scrapers which was altogether ho-hum until I saw the flow diagram for the scraping process and it got my geek on. Writing flow diagrams is darn exciting but mine end up looking like an arial view of the Colorado river as they snake back and forth. This flow is simple, effective, clean, and I like it. It also shows that it doesn’t matter what shapes you use if you use them effectively. Take that UML.

‘Scrapers’ Dig Deep for Data on the Web – WSJ.com.

Great ad about a good redesign

While reading the Marketplace section of the Wall Street Journal today I came across an interesting print ad. The ad covers a double page and on the left page is a stale, busy, overburdened design (think about.com or a SEO spam site) marked up in red pen detailing the warts, over on the right page shows the redesign of Moviefone’s website which has a clean and streamlined feel while throwing in all the features new sites seem to expect: video, boxed areas, video advertisements with supporting geo-focused information (in this case where one may find a HTC EVO phone in the financial district of San Francisco), FaceBook, etc.  Here is a poorly lit photo of the ad from my phone.

WSJ AOL Ad

At a first glance I was pulled to the gravitational force of the red pen. The criteque of the stagnant site hit home as I do this all the time; include the websites I work on where feature creep and years of add-ons have left a site that is stuck and in need of a makeover.

Of course Moviefone doesn’t have the budget for an ad like this and my assumption that the focus was on MovieFone’s 20th year anniversary was off. Turns out the focus is on AOL Advertising and a new campaign called project devil. More red pen!