Adopt microservices only when their benefits outweigh operational complexities.
Postgres, with its powerful query language and managed services, is increasingly preferred by developers.
Deep dives
The Value of Microservices Should Justify the Operational Complexity
Microservices should only be adopted when their value outweighs the operational complexity and on-call rotations that come with them.
The Importance of Limiting Microservices and Orchestrating Them Effectively
Developers should focus on limiting the number of microservices to those that provide significant benefits and ensure effective orchestration to avoid unnecessary operational difficulties.
The Evolution and Benefits of Change Data Capture
Change Data Capture (CDC) has become a crucial pattern in the movement towards real-time data processing, providing low-latency updates that enable real-time analytics and keep systems up to date.
The Advantages and Challenges of Postgres as a Database
Postgres offers a powerful and well-designed query language, making it a reliable choice for many applications. Its compatibility and improved scalability, along with the availability of managed Postgres services, make it an increasingly popular option for developers.
#214: When we first start developing applications, we probably also use a database. But at some point in time, we’ll probably hit a wall with that database because of changing business requirements. What are we supposed to do then?
In this episode, we speak with Arjun Narayan, CEO of Materialize, about of a number of items ranging from why you should move from the no-win scenario of self-hosting to fully managed services and why you may be doing too much when building and orchestrating microservices.