VSHN.timer #221: A Turning Point for Microservices?

Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.

This week we’re going to talk about those architectural decisions that can make or break your Cloud Native service.

1. Long considered the de facto approach to application architecture for cloud native services, microservices is starting to be refactored by cloud giants such as Amazon and Google. Maybe we are doing microservices all wrong?

https://thenewstack.io/year-in-review-was-2023-a-turning-point-for-microservices/

2. SQLite is often misconceived as a “toy database” because its default configuration is optimized for embedded use cases, meaning poor performances and the dreaded SQLITE_BUSY error. But what if Sylvain Kerkour convinced you that by tuning a few knobs, you can configure SQLite to reach ~8,300 writes/s and ~168,000 read/s concurrently, with 0 errors, on a ~€40/m commodity virtual server with 4 vCPUs?

https://kerkour.com/sqlite-for-servers

3. Every so often someone needs to create a more or less permanent internal identifier for their users’ accounts. Then they look at how authentication systems like OIDC return email addresses and decide that they’ll use the email address as the account’s permanent internal identification. As the famous saying goes, now you have two problems.

https://utcc.utoronto.ca/~cks/space/blog/tech/EmailAddressesBadPermanentIDs

4. SIDN manages all internet names that end in .NL. Their job is to properly manage those 6 million domain names, and technically speaking, keeping the .NL names in the air is the core competency of the organization, and also determines its future. In short, if .NL is not capable of managing .NL, that is like a restaurant buying its meals from a delivery service.

https://berthub.eu/articles/posts/your-tech-my-tech/

5. The intent of the Cloud Native Maturity Model is to help you move from inception through to full adoption of cloud native technologies using the CNCF landscape to achieve the full benefits of running scalable applications in modern, dynamic environments in public and hybrid clouds.

https://maturitymodel.cncf.io/

Are you applying the Cloud Native Maturity Model on your architecture? Are you using emails as user account identifiers? Would you like to share some architectural tips and tricks with our readers? Get in touch with us, and see you next week for another edition of VSHN.timer.

PS: check out our previous VSHN.timer editions about architecture: #25, #34, #60, #79, #143, and #201.

PS²: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.

PS³: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.