Copy
View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week, in the spotlight we have a great discussion on the future of the web on one of my favourite podcasts: ModernCTO! The main guest is Sir Tim Berners-Lee shares his vision on how to make data really personal in this world of social networks.

I found this case study on Service Mesh very interesting because not many companies are shared their journey and running a Service Mesh for a couple of years can provide valuable insights for others just approaching the topic.

After the success of last week newsletter, I decided to add an additional article on the socio technical aspect of architecture and infrastructure. Every decision we take in our software has a direct connection with the organization structure and communication flow.

Domain-Driven Design vs Demo Driven Development, an opinionated article on why often we fail to deliver software projects.

Finally, the new edition of Building Microservices, one of the best book on the topic is having a revamp and these days Sam Newman just announced the book is ready for prime time, I cannot wait to have my hands on that book.

Enjoy the read and see you next week!

In the SPOTLIGHT

The new web

Sir Tim Berners-Lee & John Bruce - Creating a New Web For All

Today we are talking to Tim Berners-Lee: the inventor of the World Wide Web and CTO at Inrupt, and John Bruce: the CEO at Inrupt.
We discuss how Inrupt is building a new layer on the Web called Solid.
How Solid’s unique API significantly reduces the need for back-end development, and how Solid gives users control over their personal data.

Case Study

Service Mesh Wars, Goodbye Istio

After using Istio in production for almost 2 years, we’re saying goodbye to it. Learn why, as well as the current state of the Service Mesh Wars.

Socio Technical Architecture

DevOps, Observability, and the need to tear down organizational boundaries

How does sportswear giant Adidas scale its operations?
Three ways: technically, culturally and strategically.

Domain-Driven Design

DDD vs DDD

After more than 20 years working in IT, the “Start coding from day one”, to me, is the biggest mistake one can make in a Software Development project. According to Domain-Driven Design principles, the developer's understanding of the domain gets distilled into code
Software Architecture

Building Microservices - 2nd Edition

Distributed systems have become more fine-grained as organizations shift from code-heavy monolithic applications to smaller, self-contained microservices. But developing these systems brings its own set of problems. With lots of examples and practical advice, this expanded second edition takes a holistic view of the topics system architects and administrators must consider when building, managing, and evolving microservices architectures.

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 😉

Opinions are my own

HELP US TO IMPROVE THIS NEWSLETTER!
We just need a few minutes of your time to make Dear Architects even better
Sure! Let me share what I think about Dear Architects!
Twitter
Website
Copyright © 2021 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