In this eMag we provide both implementation examples and comparisons of different possible approaches on a range of topics from immutable infrastructure to self-service ops platforms and service discovery. In addition, we talk about the Docker ecosystem and the different aspects to consider when moving to this increasingly popular system for shipping and running applications.
This article explains why Paddy Power adopted continuous delivery (CD), describes the resulting CD capability, and reports the huge benefits and challenges involved. This information can help practitioners plan their adoption of CD and help researchers form their research agendas.
At Craft Conference in Budapest, Dan North and Jessica Kerr presented a keynote session which cautioned developers that complexity is often found outside of the code. The key messages included: identify and manage areas of complexity; treat learning as a first-class citizen; focus on working to sustainably minimise lead time to business impact; and nurture a supportive team and community.
"Of the 4 letters in the ACID acronym, 3 of them have a different meaning than their equivalent in CAP. No wonder this is confusing. Also, the confusion does not only come from the overlaps in the wording, but in the necessity to go into the implementation details to understand the difference in a real-life concurrent application. In practice, this is one of the difficulties that had led many people (me included) to look at the ‘NoSQL’ world."
The bottom line is that Hypermedia has zero value, especially in the context of M2M (again, I am not talking about the Web’s Architecture when a human is in the loop). I am certain that someone somewhere will find an application (or two) that shows some value, just like any interesting software pattern, beyond that, hypermedia will be a big waste of time for most people, just like the uniform interface, the coupling of identity with access, http caching, verbs vs nouns, human readable documentation… have been thus far.
By now, we’ve all heard “Docker, Docker, Docker” coming from every available channel. Ok, we get it, Docker’s great. But what can you use it for? I’m not much of a detective writer, so I’m going to spoil the ending here by giving you a preview of use cases assessments from my just published “Assessing Docker and …
The driving insight is complexity grows nonlinearly with size. The type of system doesn’t really matter, but we know software size will continue to grow so software complexity will continue to grow even faster.
What can we do about it? The running themes are lowering friction and limiting risk:
Lower friction. This allows change to happen faster. Methods: dump the centralizing database; adopt microservices; use containers; better organize teams.
Limit risk. Risk is inherent in complex systems. Methods: PACT testing; continuous delivery.
Some key points:
When does software really grow? When smart people can do their own thing without worrying about their impact on others. This argues for building federated systems that ensure isolation, which argues for using microservices and containers.
Microservices usually grow successfully from monoliths. In creating a monolith developers learn how to properly partition a system.
Continuous delivery both lowers friction and lowers risk. In a complex system if you want stability, if you want security, if you want reliability, if you want safety then you must have lots of little deployments.
Every member of a team is aware of everything. That's what makes a winning team. Good situational awareness.
I think I’ve found myself (somewhat accidentally) at the beginning of a series of posts called ‘debates I find useless… let’s move on’. The latest round of discussion that seems to have spiked (at least for me) this week is the whole ‘to estimate or not to estimate’ conversation. The answer to this question clearly …
* Note: these are annotated slides aimed at making it easy to read and follow along with what I said during the session. The video will cover demos and the original unannotated deck.
We just finished the first O'Reilly Software Architecture Conference and the overwhelming most popular topic was microservices. Why all the hype about an architectural style? Microservices are the first...
Sharing your scoops to your social media accounts is a must to distribute your curated content. Not only will it drive traffic and leads through your content, but it will help show your expertise with your followers.
How to integrate my topics' content to my website?
Integrating your curated content to your website or blog will allow you to increase your website visitors’ engagement, boost SEO and acquire new visitors. By redirecting your social media traffic to your website, Scoop.it will also help you generate more qualified traffic and leads from your curation work.
Distributing your curated content through a newsletter is a great way to nurture and engage your email subscribers will developing your traffic and visibility.
Creating engaging newsletters with your curated content is really easy.