View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we have in our spotlight I'm sharing the new ThoughtWorks Technology Radar Volume 23, insights from the trenches from a great board gathering technology advice, architecture patterns and engineering practice. I found it very useful to understand the state of technology in different industries different from mine.

Netflix Tech blog is very active and this week they released a new post on how they deal with big data in a distributed system environment, there is always something to learn from them.

Continuing with our Domain-Driven Design series, I found useful revisiting some domain-centric architecture, I think this post could lead you to investigate your favourite one, mine it is the hexagonal architecture, what is yours?

Communication in distributed systems is always challenging, in this article you can find some food for thoughts on how to use events for better decoupling your architecture.

Finally, I thought to share another post on disaster recovery, I feel we often forget or deprioritize this important topic that should be in the centre of any architectural discussion.

I hope you will find them useful, enjoy the read!



Technology Radar

The Radar captures the output of the Technology Advisory Board’s discussions in a format that provides value to a wide range of stakeholders, from developers to CTOs. The content is intended as a concise summary
Big Data

Batch Data Moving from Data Warehouse to Online Key-Value Stores

Netflix has more than 195 million subscribers that generate petabytes of data everyday.
Domain-Driven Design

3 Domain-Centric Architectures Every Software Architect Should Know

The first concern of the architect is to make sure that the house is usable, it is not to ensure that the house is made of brick. — Uncle Bob
Distributed Systems

Event Notification vs. Event-Carried State Transfer

As we move into a world where distributed systems are the norm and monoliths the exception, one of the key architectural decisions to make is around the mechanics of inter-service communication. 
Disaster Recovery

Failing over without falling over

As applications move online and digital automation extends to control more of the physical world around us, software failures have an increasing impact on business outcomes and safety. We need to develop more resilient systems, and that can’t be left as an operational concern.
Thanks for reading Dear Architects 🙏

If you have any suggestions to make this newsletter better, just drop us an email!

Have a great rest of the week 😉
Copyright © 2020 deararchitects, All rights reserved.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp