Click here to close now.


Microservices Expo Authors: Yeshim Deniz, Jason Bloomberg, Carmen Gonzalez, Elizabeth White, Liz McMillan

Related Topics: @CloudExpo, Java IoT, Microservices Expo, Containers Expo Blog, Release Management , @BigDataExpo, SDN Journal

@CloudExpo: Blog Feed Post

What You Read Says a Lot About You

A far greater percentage of my time has been spent reading about computer science

It is interesting, talking with people about what they read, and seeing how what they read is reflected in their daily lives. Even the occasional reader of this blog would not be surprised to find that I spend some amount of time with my nose buried in epic fantasy books and military history books. It shows in much of how I carry myself, what I do for hobbies, and even the examples I choose in this blog.

But a far greater percentage of my time has been spent reading about computer science. Since I was a young teen, those were avocations, I wanted computers to be my vocation. So it should surprise no one that I devoured what can arguably be called the classics of our field – Norton’s hardware programming books, compiler theory books (used one book in each of my post-secondary degrees, own dozens, literally. Compilers and OS Design fascinate me), some of the Cisco stuff, MicroC/OS, the dragon book (worth mentioning separate from the other compiler books), the J2EE books by BEA, Norton’s security book, the list goes on and on, and gets pretty eclectic. I read “Implementing CIFS with relish, though I may be the only person on the planet that did, and I have several releases of CORBA docs, all read at one time or another in the past…

But with two of us (Lori is a pretty voracious reader also), we have amassed a collection of Comp Sci books that cover three shelves and fill another closet that is three rows of books deep and shelves every 12 inches. And we don’t read them all. Some were useful at one time – the early Obfuscated C books, Fedora 2, The Tao of Objects, Perl 5… Many of the aforementioned books. Some were never real useful. Mastering Web Services Security, for example, was not such a great read when it was new. Nor was Programming Language Landscape.

And thus, we’ve been going through the painful process of determining what to keep and what to lose. While some of these we can get on our kindles, not all of them. Some of our current collection of programming books (every Android book we own, for example), are on Kindle, but most are not, and many are not available on Kindle at this time. So we’re making the actual “we will use this, we won’t” decision.

Some of the decisions were easy. We don’t use Borland IDEs anymore, so we really don’t need the three copies of the documentation we had laying around. Two of them went. Some weren’t so easy. Operating Systems Design, The Xinu Approach is a rock-solid book with some great examples, but Linux and FreeBSD have kind of blown the bulk of the need for it out of the water. Sure, we might refer to it some time, but probably not. The various IT leadership books we’ve earned by virtue of going to management training over the years? Yeah, most of those can go, but a couple had rock-solid stand-the-test-of-time themes to them. Collected papers of various IEEE and ACM subgroups? Those are always an astounding read. The Risk subgroup, back when it focused on “people will die if this is wrong” was great, those papers are a good read… But not likely to be useful, and we really do need the shelf space.

So how’s it working out for us?

Well, we’re not done yet, but we’re set to condense all that space into a single 4’ tall bookshelf. At this point, our selections are broad enough that I can tell you what the pattern is. There’s overlap in all of these, no one section came 100% from one of our choices, we both contributed to them. They are:

Management Books – both funny and serious, from Dilbert to Peopleware

Networking Books – We both still do a lot with networking, so it makes sense that things you rarely see massive change in, we’d keep reference to. From a Cisco introductory text to TCP/IP Illustrated, Vol 1.

Web Dev Books – This is a pretty interesting space, because much of this we have done electronic, so what we have in print was important to us for some reason. from JavaScript to Lori’s XAML book to an XSLT and XPATH reference.

AI and Neural Networks – This space is largely Lori’s playground, but a small collection of focused books on the topic, with fuzzy networks in C++ being my favorite.

Data Structures and Operating Systems – From Lori’s favorite Introduction to Algorithms to my pet Reusability and Software Construction in C/C++, there are about a dozen of these, we tended to lean toward overview type books, but some of the OS ones are pretty deep.

Hardware – I’m still a fan of embedded programming, there is computer architecture, and hardcore networking development requires hardware references… So this section is pretty big, from MicroC/OS-II through Computer Architecture: A Quantitative Approach.

Languages – Books we cannot, or do not want to, do without. Strostroup on C++, a LiSP reference, Kernigan and Ritchie, Java architecture, and assembly language, and that's just the tip of the ice burgh.

Compilers – I admit it, this is my bit, just like AI is Lori’s. She reads some of them, and enjoys them, but I’m a bit of a freak on the topic, having written compilers and linkers, just to prove to myself I could. From the COFF format to Modern Compiler Implementation in Java, We’ve got a score or so of them. Great bedtime reading.

What would you keep? If you had to cut your book collection to about 10% of what it currently is, what would go? We had Java books and XML books that we never even got out of the shrink-wrap, because the online references were so good. No doubt you have the same… Those can go, if you’re never going to read them. :-)

So what it says about us is that we’re geeks. We kept four (possibly five, I can’t decide on “The Leadership Challenge”) management books, and so far have dozens of books only a geek could love. By the end, we’ll have completely filled that little shelf, but we’ll have unloaded a ton of unnecessary books. That’s all good to me. And hey! In the process, I found some military history books I was looking for. No idea how they ended up stacked between calculus and Red Hat 2.0, but there they were (in the picture, top shelf). Now to find time to read them… And to finish going through that half-done closet in the picture.

Read the original blog entry...

More Stories By Don MacVittie

Don MacVittie is currently a Senior Solutions Architect at StackIQ, Inc. He is also working with Mesamundi on D20PRO, and is a member of the Stacki Open Source project. He has experience in application development, architecture, infrastructure, technical writing, and IT management. MacVittie holds a B.S. in Computer Science from Northern Michigan University, and an M.S. in Computer Science from Nova Southeastern University.

@MicroservicesExpo Stories
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction....
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Achim Weiss is Chief Executive Officer and co-founder of ProfitBricks. In 1995, he broke off his studies to co-found the web hosting company "Schlund+Partner." The company "Schlund+Partner" later became the 1&1 web hosting product line. From 1995 to 2008, he was the technical director for several important projects: the largest web hosting platform in the world, the second largest DSL platform, a video on-demand delivery network, the largest eMail backend in Europe, and a universal billing syste...
Docker is hot. However, as Docker container use spreads into more mature production pipelines, there can be issues about control of Docker images to ensure they are production-ready. Is a promotion-based model appropriate to control and track the flow of Docker images from development to production? In his session at DevOps Summit, Fred Simon, Co-founder and Chief Architect of JFrog, will demonstrate how to implement a promotion model for Docker images using a binary repository, and then show h...
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively.
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
DevOps Summit at Cloud Expo 2014 Silicon Valley was a terrific event for us. The Qubell booth was crowded on all three days. We ran demos every 30 minutes with folks lining up to get a seat and usually standing around. It was great to meet and talk to over 500 people! My keynote was well received and so was Stan's joint presentation with RingCentral on Devops for BigData. I also participated in two Power Panels – ‘Women in Technology’ and ‘Why DevOps Is Even More Important than You Think,’ both ...
In a report titled “Forecast Analysis: Enterprise Application Software, Worldwide, 2Q15 Update,” Gartner analysts highlighted the increasing trend of application modernization among enterprises. According to a recent survey, 45% of respondents stated that modernization of installed on-premises core enterprise applications is one of the top five priorities. Gartner also predicted that by 2020, 75% of
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Our guest on the podcast this week is Jason Bloomberg, President at Intellyx. When we build services we want them to be lightweight, stateless and scalable while doing one thing really well. In today's cloud world, we're revisiting what to takes to make a good service in the first place. Listen in to learn why following "the book" doesn't necessarily mean that you're solving key business problems.
For it to be SOA – let alone SOA done right – we need to pin down just what "SOA done wrong" might be. First-generation SOA with Web Services and ESBs, perhaps? But then there's second-generation, REST-based SOA. More lightweight and cloud-friendly, but many REST-based SOA practices predate the microservices wave. Today, microservices and containers go hand in hand – only the details of "container-oriented architecture" are largely on the drawing board – and are not likely to look much like S...
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at, and Tomer Levy, co-founder and CEO of, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the archi...
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attende...
With containerization using Docker, the orchestration of containers using Kubernetes, the self-service model for provisioning your projects and applications and the workflows we built in OpenShift is the best in class Platform as a Service that enables introducing DevOps into your organization with ease. In his session at DevOps Summit, Veer Muchandi, PaaS evangelist with RedHat, will provide a deep dive overview of OpenShift v3 and demonstrate how it helps with DevOps.
All we need to do is have our teams self-organize, and behold! Emergent design and/or architecture springs up out of the nothingness! If only it were that easy, right? I follow in the footsteps of so many people who have long wondered at the meanings of such simple words, as though they were dogma from on high. Emerge? Self-organizing? Profound, to be sure. But what do we really make of this sentence?
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.