Software Architecture Newsletter #2
Welcome to the 2nd edition of the Software Architecture Newsletter!
First – thanks for the great feedback on this newsletter! A lot of you have reached me, either by mail or DM, and told me they really like it, and have been waiting for something like this. So thanks for that!
As usual, if you found something interesting that you think should be included here, or you have something to say about the content of this newsletter – drop me a mail at email@example.com
So, without further ado – here’s the 2nd edition of the Software Architecture Newsletter.
Flutter vs React Native – True, we Software Architects are generally concerned with what’s happening in the back end, and don’t really mind what those UI/UX/U-something do in the front end. After all, a real Software Architect’s front end is the API.
But – part of our job is to help with the technology stack, which includes, apparently, the front end.
And here, we find some strong contenders in the mobile cross-platform field. We have ionic (which kind of lost traction lately), React Native and Flutter. I have my personal favorite (and it does not begin with R), but actually they’re both great.
In this article you’ll find a very comprehensive analysis of the two, laid out in a clear and concise way. It’s one of the best articles I found on this topic, and I highly recommend it.
Read it here.
Microservices Observability Pattern – One of the best things about Microservices is their modularity. Instead of having one, ominous monolith, we have a lot of small services, each deployed independently.
One of the worst things about Microservices is the need to monitor the little devils.
It’s extremely easy to find out if your monolith has stopped working. It’s something else entirely to figure out whether all your 213 services are up and running.
And in order to do that we, the architects, must adopt observability patterns.
In this great article on Hackernoon this pattern is described, with a great emphasis on logging, one of the corner stones of every observable system.
Why the Serverless Revolution Has Stalled – Serverless is all the rage right now, and we hear about it all around us.
But – I’m not sure all is rosy in the Serverless realm (and of course – never forget this).
In this interesting – not to say provocative – article, Bernard Brode of InfoQ argues that Serverless is far from delivering on its promise, and counts various reasons for that. Even if you built your own system only around Serverless resources – it’s a must read for anyone considering using it.
Read the full article here.
Microsoft Announces Modular Azure Datacenter – Ever wondered what to do with that empty space in your garage? Well, fear no more, because Microsoft has a pretty good idea for you.
Microsoft announced the general availability of the Modular Azure Datacenter, or, if you will, Azure in a Box (a pretty large one, though).
MDC is a transportable, durable, pre-packaged cloud solution, that can bring Azure capabilities to literally every corner of the globe. Just plug the thing in, connect it to the network (actually – that part is optional. MDC can operate in a fully disconnected mode) – and voila, you have Azure humming along in your backyard.
The value of such offering is actually quite clear and immediate. There are a lot of organizations who would like to enjoy Azure capabilities, but don’t want to use the public cloud datacenters, either because of data confidentiality or even because of costs, not to mention the need to sometimes operate in god-forsaken locations. For these potential customers – MDC provides an immediate, cost effective value.
Read the full announcement here.
5 Key Learnings From Working with JWT – JWT is the de-facto standard protocol for moving authentication & authorization data, and most modern apps use it to validate their users’ identity.
However, there are some things that must be considered when using it.
This article highlights some of them, and I would encourage you to take a look. Yes, most of it is just common sense, but then – isn’t it all?
What is Infrastructure as a Code? – Part of a lot of DevOps pipelines is to build – and destroy – infrastructure elements, such as VMs, disks, etc. This is needed mainly for testing, when we want this infrastructure to test the code, and then – we don’t need it anymore.
But how can we manage infrastructure as part of DevOps automation?
The answer lies in Infrastructure as a Code.
This article from TheNextWeb (by Milecia McGregor) provides great intro for IaaC, and if you have anything to do with DevOps – it’s a real Must Read.
Concurrency – What a beloved topic, isn’t it? Who doesn’t like some concurrency issues sprinkled on his shiny new app?
A question about concurrency was asked in our Facebook Group, and the variety of answers was overwhelming. Want to chime in? Do it here.
Black Friday Sale!
So black Friday is upon us, and to indicate this event, I’ve put all my courses on a special sale, which begins right now!
You can grab all my Software Architecture courses for special prices, from 9.99$ – 11.99$.
Tens of thousands of students already enrolled in these courses, and became great Software Architects.
The sale ends in 5 days, so you better act fast…
Here are the courses on sale:
The Complete Guide to Becoming a Software Architect
Microservices Architecture – The Complete Guide
REST API Design – The Complete Guide
Software Architecture Case Studies
Software Architecture Security – The Complete Guide
Remember – the sale ends in just 5 days, and the coupons are limited, so act fast!
So, that was the second edition of the Software Architecture Newsletter (temp name).
I hope you enjoyed it, and feel free to suggest and comment on it, simply by replying to this mail.
Also, if you created a unique content you think can be included here – drop me a note!
Looking forward for your feedback!