HackerTrans
トップ新着トレンドコメント過去質問紹介求人

techthumb

no profile record

投稿

Revel - a ride share service in NYC shuts down

gorevel.com
5 ポイント·投稿者 techthumb·11 か月前·0 コメント

Nasdaq/Verafin: AI Leader in Financial Crime Prevention

verafin.com
1 ポイント·投稿者 techthumb·12 か月前·1 コメント

コメント

techthumb
·3 か月前·議論
Amazon Bedrock Mantle provides OpenAI compatible API endpoints for model inference, powered by Mantle, a distributed inference engine for large-scale machine learning model serving. These endpoints allow you to use familiar OpenAI SDKs and tools with Amazon Bedrock models, enabling you to migrate existing applications with minimal code changes—simply update your base URL and API key.

https://docs.aws.amazon.com/bedrock/latest/userguide/bedrock...
techthumb
·12 か月前·議論
Machine Learning capabilities analyze vast volumes of financial data, including transactions and check images to detect unusual customer behavior and suspicious activity with high accuracy and fewer false positives.
techthumb
·4 年前·議論
Transaction boundaries are a critical aspect of a system.

I've often noticed that these boundaries are not considered when carving out microservices.

Subsequently, workarounds are put in place that tend to be complicated as they attempt to implement two phase commits.
techthumb
·4 年前·議論
NASDAQ has moved the matching engine to AWS Outposts

https://www.nasdaq.com/press-release/nasdaq-completes-migrat...
techthumb
·4 年前·議論
There's also https://jless.io
techthumb
·4 年前·議論
K8S is not easy.

  It helps standardize:
    - deployments of containers
    - health checks
    - cron jobs
    - load balancing
What is the "old way" of doing things?

Is it same/similar across teams within and outside your organization.

If not, what would it cost to build consensus and shared understanding?

How would you build this consensus outside your organization?

For small organizations, one should do whatever makes them productive.

However, as soon as you need to standardize across teams and projects, you can either build your own standards and tooling or use something like K8S.

  Once you have K8S, the extensibility feature kicks in to address issues such as:
   - Encrypted comms between pods
   - Rotating short lived certificates
I don't love K8S.

However, if not K8S then, what alternative should we consider to build consensus and a shared understanding?