This is the fourth and last post in a series on cloud conventions and innovations. In the previous post, I set the groundwork for cloud on mainframe by making a case that mainframes are an excellent place to host Linux images. Since cloud is more than Linux, in this post I will share more details on a mainframe-based cloud service.
Posted: October 26, 2015 |
This is the third post in a series on cloud conventions and innovations. In the first two posts, I discussed a number of attributes of cloud including quickness, cost and price, upkeep, shared use, ease of working, and scaling up and down. These attributes are used to boast about the benefits of cloud services but are also a key part of the value of mainframe computing.
Posted: October 19, 2015 |
This is the second post in a series on cloud conventions and innovations. As I discussed last week, some characteristics of cloud are simply conventions whereas other features are new and innovative. Many of the characteristics of cloud computing are like mainframe computing, as both utilize centralized computing technologies like virtualization and approaches like providing systemwide backup and database management.
Posted: October 12, 2015 |
This is the first post in a series on cloud conventions and innovations. Some characteristics of cloud are simply conventions—the way things are done—whereas other features are new and innovation. The difference and context for these contrasting characteristics and features is the subject of this series of posts.
Posted: October 05, 2015 |
This is the last post in this brief two-part series on DevOps. DevOps was discussed in my previous posts on microservices so I explored it in this two-part series. In this post I survey some of the tools that align with DevOps to make it even more useful as a method to develop applications.
Posted: September 28, 2015 |
This is the first post in this two-part series on DevOps. DevOps was discussed in my recent blog posts on microservices so it was natural to take some time to explore it in more detail. DevOps is formed from development and operations, two phases associated with applications—develop them then pass them to operations for support.
Posted: September 21, 2015 |
This is the final post in this series on microservices. In the first post, I wrote about the design attributes of microservices, and in the second I wrote about how those characteristics aligned with cloud platform services. This post is about the lifecycle context for microservices. I use DevOps steps to organize the discussion of the lifecycle of microservices applications. DevOps is a collection of concepts, practices and tooling, as well as team organization that makes it more straightforward to get new applications and their updates deployed rapidly. Here’s a good introduction to the topic.
Posted: September 14, 2015 |
This is the second post in this series on microservices. In the first post, I wrote about the design attributes of microservices. In this post, I write about how those characteristics align with cloud platform services.
Posted: September 07, 2015 |
This is the first post in a series on microservices, which is primarily an application design method or way of approaching the organization and conventions utilized when developing a complex application.
Posted: August 31, 2015 |
This is the last post in this four-part series on high availability (HA). The focus of this post is HA in the cloud, which is challenging to discuss because the cloud is different depending on many factors. The cloud is different as it varies widely by service provider, i.e., IBM SoftLayer is significantly different from Amazon Web Services. The cloud is also different if you do it in house yourself with your own hardware and software integration or use ready-made Infrastructure as a Service like IBM PureSystems offerings designed to be up and running out of the box in as little as four hours.
Posted: August 24, 2015 |