Couldn’t find any info on periodic famines at that area. Do you mind sharing any clue, like name, specific area, years? Genuinely interested.
On communist part. Ukraine SSR was established in 22, Holodomor started in 32. Famine in Tatarstan started in 21, year after Tatar ASSR established. So something not adding up. Even if one ignores those. There were no famines after USSR collapse in both areas. Feel free to point one if I’m missing something.
I’m still not totally understanding what you’re looking for. But if you need alternative to JS for writing web UIs check out htmx. It’s still JS lib but its main goal to facilitate hyper text as engine. Meaning you do SSR but with CSR UX. And it’s backend agnostic.
Container update is not Docker’s concern. Docker is proxy between your Container and OS. So if you want keep your container up to date you need external process. Can be achieved with container orchestration tool like Kubernates
I don’t understand too. Are you suggesting me to drop bunch of features in the product?
Is it better than React functional components in any way? I don’t see benefit over React functional components or even Lit’s class components
I don’t know german but it seems to be more logical to have one word for “health insurance card” since it describes one class of objects. Better than spelling 3 nouns where one partially describes what object is and other nouns act like clarification
Though in reality, management will push back any unorthodox approaches/solutions/approaches as risk and additional losses on R&D.
Why sit there 5 mins? This looks like normal city bus stop. Bus arrives at scheduled time, picks up passengers and takes off. I believe great ‘merica supper power nation can manage what Eastern Europe nations made happen years ago. Yes you may have few mins delays but it’s not a disaster.
If for whatever reason it must sit there for long time bust stop should be in a bay
MAYBE :)
First of all, what you are doing is integration via DB. Unless that was conscious, I would avoid using this approach. System is much easier to manage when DB/schema used at most by one app. You have two ways to achieve it, move towards micro-services or monolith. Yes monolith is still great for some use cases.
If we talking about your current system state every app should do changes in most backward compatible way. It worst cases it will lead to duplications. Let’s say if you want to change table X because there is such need for app A and at the same time app B uses this table. Instead of modifying X you create table Y that satisfies needs of A and make sure that data written into Y as well as into X to maintain B.
Does API actually doing anything or it’s pass-through to data source? You could request data feed and build adequate API on your side