Build and Deployment Patterns

One of my favorite topics in the Software Engineering realm is configuration management, and my favorite subtopic within that would be build and deployment patterns — i.e., what are the best practices around building and deploying software.

Ken Mugrage has written a fantastic post on this subject for the DevOps section of the DZone site that echoes at least three of my personal build and deployment mantras:

  • Build it once
  • Develop and Test on the same platform as Production
  • Always know which version(s) are running on each environment

I spent several years studying and developing build and deployment patterns and building tools to support them, long before it was called “DevOps,” while at the same time developing and maintaining software in a team environment, so I can attest to the fact that these patterns work and that they can save you a lot of time.

I hope you enjoy “5 Key Deployment Pipeline Patterns” by Ken Mugrage.

Modeling RESTful Services with RAML

If you’ve done much development, design, or research in the area of web services in the past ten years, you have most likely encountered the term RESTful services or at least the REST acronym, unless you’ve been living under a rock. [And let’s face it, if you have been living under a rock — not that there’s anything wrong with that —  it’s doubtful that you have had much involvement with web services, so there you go.]

RAML stands for RESTful API Modeling Language and is built upon the YAML and JSON standards. If software engineering or design is your thing, and you are faced with designing and/or developing RESTful services, then I would encourage you to learn a little about RAML. A good starting point is Introduction to RAML – The RESTful API Modeling Language, an article that I wrote recently for Baeldung.