As an older coder, past my 40s, the industry hasn’t forgotten, it’s just moved on.
Distributed transactions across many microservice is too inefficient and complex to deal with. DT is fine if you don’t have microservices, scaling out quickly is hard otherwise.
Session cookies likewise ~ how does authN and authZ work through each microservice without overloading a central service? JWTs do decently.
Don’t use microservices? That’s a different debate.
>Distributed transactions across many microservice is too inefficient and complex to deal with. DT is fine if you don’t have microservices, scaling out quickly is hard otherwise.
Perhaps microservices were the wrong idea then... Added complexity and splitting what is still conceptually a single coordinated operation.
>Don’t use microservices? That’s a different debate
If it's the proper debate though, we should get to it - not just ignore that part, and say "we moved on", as if we improved things...
There is no we: everyone does it different. The term engineering that we stole from engineers implies making pragmatic decisions based on cost, complexity and requirements. Honestly I see the erring on the side of the traditional more than I do the extavagent in real life.
I joined Datadog after the Vector acquisition and now currently am the manager for the Community Open Source Engineering team that works on Vector open source.
Just confirming strongly what ripley12 said, as a person with direct involvement in OSS at Datadog.
I joined Datadog after the Vector acquisition and now currently am the manager for the Community Open Source Engineering team that works on Vector open source.
It’s def. not deprecated, but it did take awhile to sort out. It’s not easy figuring out business vs giving away software for free.
Anyways, there’s quite a few issues and GitHub discussions everyday, in addition to Discord chats.
I've personally found that even when I do my best to exude interest in the industry/company through custom question responses or the cover letter that auto-rejection is still the most common end result.
I'm still amazed that the applicant tracking systems don't provide employers with stats like "time spent on application" or "time spent on website researching". At least this would be a signal towards higher interest.
Heck, I'd love a "fave 5" system for employers. Something to flag extreme interest in working for their company. Companies would probably love to have a list of high-intent people to recruit, regardless of their current employment status.
wouldn't poeple just flag everything as their fav 5 and put high numbers of hours not actually spent on the application? unless the system can track all a candidates applications, this seems moot, and if it did track all that yuk no thank you, i don't need more tracking in my life to solve a problem we created artificially. Plus it is probably easy to game for anyone with a minimum of programming skills...
The thought process was tracking all candidates (not having a user-submitted number). That tracking is already happening for most marketing analytics. I'm surprised I haven't seen it show up on the job application side.
As for the fave 5 idea - I don't see an easy way to game this if it's tied to a single user account. You would only be seen as prioritizing the company to the employer if you're actively prioritizing them. Most people are applying to way more than 5 companies simultaneously and don't know where their application stands for the company. It would be too risky to try and rotate it continuously.
Also (at least in Southern California) electricity prices and how long the rig is on. Not as bad as the initial build cost, but run costs will add up over time.
Except, how long does it take to throw the code away? Sometimes never.
Write short designs; Goals, constraints, options. Prevents the tech debt from building over time and signals better when to throw chunks of systems away.
Distributed transactions across many microservice is too inefficient and complex to deal with. DT is fine if you don’t have microservices, scaling out quickly is hard otherwise.
Session cookies likewise ~ how does authN and authZ work through each microservice without overloading a central service? JWTs do decently.
Don’t use microservices? That’s a different debate.