“Separating the concepts of deployment from release is important. Just because software is deployed into a given environment doesn’t mean it’s actually being used by customers.” -Sam Newman, Monolith to Microservices.
#microservices #deployment #release

So we are building a system from scratch which should have a #Microservices architecture.

I strongly recommended to take #rust #rustlang into consideration as programming language.

Does anyone know if there is something like resilience4j available for Rust to reduce manual effort making the services resilient? Or do have general advice regarding this topic (like blog posts etc.)? Thank you very much in advance.

Probably for the majority of use cases (uniformly randomly selecting among all software projects), #monolithic architecture is a better fit than #microservices architecture.
https://nebu.substack.com/p/when-to-use-microservices-vs-monolithic?sd=pf

Breaking Changes in Microservices – 📘 Neuer Artikel von Sascha Feldmann
#microservices
https://www.informatik-aktuell.de/entwicklung/methoden/breaking-changes-in-microservices.html

Eine auf #Microservices basierende Architektur umzusetzen bedeutet, dass auch die Datenhaltung auf die verschiedenen Services verteilt werden muss. Was aber bedeutet das in der Praxis? Was ist, wenn Daten einer Entität - vollständig oder in Teilen - in mehreren Services benötigt werden?

Dies sind nur wenige von vielen Fragen, die in der Session von Lars Roewekamp beantwortet werden. So viel vorab: Umdenken ist gefragt!

https://www.oop-konferenz.de/oop-2023/programm/konferenzprogramm#item-5193

#softwarearchitektur #datapitfalls #monolith

Many of them have misconceptions between Microservices and APIs. They are not equivalent and play a completely different roles in web applications. In this article, you will clearly understand the difference between Microservices and APIs. https://www.anblicks.com/blog/difference-between-microservices-and-apis/

#api #microservices

What I'm not expecting to get from transitioning to #container #docker #microservices :

* Cost savings -- the current system is cheap because we have so few users. The new system will be hugely overengineered for 30 users and will cost more, but will leave opportunity for growth.

That's about it -- thanks if you've read this far. Open to any comments/questions/anecdotes -- this site has always been as much a learning experience for me as anything else. (9/9)

* Security -- with the reverse proxy in place, I can expose only the endpoints that clients need, while hiding other endpoints for internal use only. This also completely wipes away some questionable design choices made early on when I didn't know what I was doing.
* Easier user management - so stoked to get #keycloak doing user management here. I initially implement #facebook OIDC intergration and fml on that and eff the Facebook SDK.

#microservices #docker #container (7/?)

What am I hoping to get from all this work?

* Easier maintenance. The app was initially designed as a single-user client app, and certain implementations of things did not scale well to a multi-user web app environment. Redesigning these things is impossible today because it's written into one #Python library shared by 50+ separate endpoints. This will segment the logic of various processes and hopefully make future redesigns feasible.

#microservices #Docker #container (6/?)

The three other #microservices I have -- one is a chat feature on the site. I haven't started rewriting this yet. The other is aggregate user stats -- leaderboards, awards, that sort of thing. This data is in #MySQL; lots of read/write, lots of different queries, joins, aggregation, etc. The last is the quiz management service; this glues the other services together to provide the right output for the client. And that's it, all this, plus the front end / reverse proxy container. (5/?)

I'm integrating a #keycloak instance to replace my own user auth implementation. One thing here is I can implement user preferences as attributes in keycloak. Those can appear in the signed jwt client-side, which is pretty nifty. I just need to make sure that none of them need to be joined with the other data in #MySQL. Also, there's a separate service that interfaces with keycloak to let the user update prefs through the front end. #microservices (4/?)

Similarly, I have the #scrabble word list as a data source. It is 297,077 rows of read-only data. I've taken this out of #MySQL and put it in a separate #MongoDB container, and again anything that needs to query this data goes through the "lexicon" service assigned to it #microservices (3/?)

One thing I tried to keep in mind when designing these #microservices is to map one microservice to one data source. My site is an app where users can study the #scrabble dictionary. For legacy reasons (that are still valid), user study data is stored in a #SQLite database (separate DB file for each user). So everything that needs to touch a user's SQLite DB has to go through the service assigned to it. (2/?)

Some thoughts on my website rewrite. Currently the back end is a collection of python cgi scripts run by Apache; there's probably close to 50 of them. I'm grouping these into six containerized microservices.

How do you decide what endpoint goes in what #microservices? What a great question -- the answer is, I have no idea and am completely guessing. (1/?)

Musk vs #MicroServices

RT @shanselman
Twitter seems to be randomly unfollowing people I’ve followed for years. #microservices

@preslavrachev @inanc We have migrated several #Microservices from #java to #golang . They are faster and need way less ram than the Java docker container version.
I think it's going into the right direction - also with ui toolkits like #fyne for example.

https://www.youtube.com/watch?v=y8OnoxKotPQ lol #microservices #Dev #development #cs #programming #funny #software #softwareengineering

Today, we launch '22 @jakartaee gifts for 2022!' In its last month, we celebrate the year's best content.

To kick off, Ralph Soika in January: 'Is Spring Boot Still State of the Art?' He believes Jakarta EE is better when migrating to a #microservices :
https://ralph.blog.imixs.com/2022/01/05/is-spring-boot-still-state-of-the-art/?utm_content=229547641&utm_medium=social&utm_source=twitter&hss_channel=tw-2599580401

#springboot #javaee

Are there #rust jobs that aren't #crypto or #finance related? How come there isn't stuff that's about writing #microservices in Rust, or media processing, or other things that require performance? Is rust just too young?