At least in the case of the Digital Euro, one of the explicitly documented goals for the scheme is to alleviate dependence on US payment processors within Europe
I'm fairly noobish at understanding all this stuff, but as I understand it there are severe structural issues with the existing banking system that make a completely new mechanism desirable. For example by depositing cash into traditional accounts, it is also equivalent to providing capital to traditional banks to loan from. It would therefore be difficult to supply cash to end users without also increasing the availability of credit, which may be undesirable for any number of policy reasons.
> The experience with pandemic emergency payments has brought forward an idea that was already gaining increased attention at central banks around the world, that is, central bank digital currency (CBDC). Legislation has proposed that each American have an account at the Fed in which digital dollars could be deposited, as liabilities of the Federal Reserve Banks, which could be used for emergency payments
The problem is Lenovo machines look and feel like PCs, and that's not a complement. I got the XPS specifically for the trackpad, its the only one around that I know of that handles any way remotely like a MacBook's.
I moved to XPS 15 as my first non-Mac machine in over 10 years, and I must say I'm far from impressed by the build quality.
These laptops are gorgeous new, but they are SO fragile. One of the screen hinges is broken, I've replaced numerous keys, the keyboard is now developing some debounce/key registration issue all over the right-hand side, the speakers are both blown (left first then the right), the trackpad sits 0.5cm above the case (needs replaced), the glue holding the rubber to the bottom of the case expanded with heat and leaked out everywhere. Probably more I've forgotten
I'd still consider buying another, but I'd also strongly consider changing vendors once this machine finally dies
Noticed this a few times, where race is associated with some bad behaviour as if it made matters any worse. What does it matter if the developers were Turkish?
edit: are the downvotes because you believe race matters in this case, or some other problem with the comment?
For single node sure, but the moment you have some set of jobs requiring a multi node setup, the chance of wanting to find yourself in a situation where the cluster has essentially bricked itself due to a momentary power outage reduces to zero really quickly.
The only place etcd might not pay off is in disposable dev environments or something, but do you really want your prod setup to page only to discover a complete cluster rebuild is necessary to resolve the problem?
Classic bait-and-switch. This essentially happens with every review site after they build up enough brand awareness to pull it off. I guess it happens because from the perspective of the company it makes total sense to try. Why earn pennies on the dollar from e.g. ad clicks when you can get huge lumpy (and possibly regular) payouts for much less work in much less time
It was intended more to invoke general ideas about management ease than being a specific remediation, however
elsewhere in the thread there is an example of a diagramming tool split out across 37 individual AWS services/service instances. In a traditional design, this is conceivably something where all state and execution could easily fit in one VM, or perhaps one container with the state hoisted off to a managed service. In this case we could conceivably fix some problems with an app like that literally just by kicking the VM
AWS in particular seem to have a carefully refined technical sales/certification/advocacy channel whose main product is those fucking stupid architecture diagrams. Hello world service with $4000/mo. worth of geo-replicated backing databases, CloudWatch alarms, API Gateway instances, WAF etc.
But don't let it encourage you to think serverless has no value, or it can't be done portably or cheaply. It has its sweet spots just like everything else.
It's not clear to me how much experience with serverless architectures the author of the parent comment has, but speaking as someone with plenty, the operational costs of serverless are at least equal to managing stateful infrastructure, with much less control when things go wrong. Lambda was a major step up in long term predictability compared to for example App Engine, where there have been plenty of instances of overnight unannounced changes, or changes announced with incredibly short notice period, requiring developer time rather than ops time to bring an application back to service.
On the ops side even with a platform like Lambda, training an operations team to take over maintenance of a nested spaghetti of random interlinked services and bits of YAML trapped in random parts of the cloud is a total nightmare. The amount of documentation required and even the simple overhead of enumerating every dependency is a long term management burden in its own right. "The app is down" -> escalate to the developers every single time.
Compare that to "the app is down", "this app has basically no ops documentation", "try rebooting the instances", "ah wonderful, it came back"
I'm pro-cloud in many ways and even pro-serverless for certain problems, but let's not close our eyes and pretend dumping everything into these services is anything like a universal win.
They've all had this almost since basically prehistory (e.g. mod_proxy_lb). The process management bit not so much, but having a web server manage app server processes, that's an abstraction I could live without
Hmm, this is true. Another way to think about it perhaps is that, I don't think any race can be avoided just by slowing things down somehow, the rules of the game are only slightly changed in that case, and perhaps not in a way that has any benefit to slower traders.
For example at IEX when they introduced their speed bump, it was to protect their so-called 'mid peg' hidden orders. What they found was that these orders were still the target of adverse selection because some HFT trader could submit speculative orders well in advance, by predicting price movements based on fast information from connectivity to the order books of other exchanges.
That PDF is an awesome read ( https://iextrading.com/docs/The%20Evolution%20of%20the%20Cru... ), but I think it speaks to a more general problem of trying to slow down. Even if auctions on all exchanges only occurred once every 10 seconds, there will still always be an advantage to whoever can aggregate information the fastest and use this to submit a best price at the latest possible moment to participate in the auction.
In my uninformed state, it doesn't seem possible to truly reverse this process, and I'm left wondering what problem would be solved by attempting to eliminate HFT from the markets
I remember this :) scgi, FastCGI, uwsgi, probably gunicorn has its own too.. never quite understood the obsession with inventing mini protocols once you have a persistent server process running already and can just use HTTP proxying. They're a pain in the ass to debug and no real tooling for poking at them.
Order-triggered auctions are slowly becoming a thing, but they have limits too. In this scheme, everyone submits an order and e.g. once every 100ms the exchange will cross them. Very little understanding of them, but they look cool