https://docs.aws.amazon.com/bedrock/latest/userguide/bedrock...

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.

https://www.nasdaq.com/press-release/nasdaq-completes-migrat...

I hate AWS with a passion.

When I have large blob of json, I am usually interested in first getting a high level idea of how it is structured (first few levels) then I either need to drill down or filter to find what I need. The combination of jless for interactive exploration and jq to make it easily scriptable/repeatable is quite nice.

I find it natural to reduce the json I start with to a subtree I can make sense of, and thus don't find myself lacking a tool which can provide a visual representation of the complete dataset.

  It helps standardize:
    - deployments of containers
    - health checks
    - cron jobs
    - load balancing

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

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

From a moat perspective, I wonder if the TAM of this business in the context of the three cloud providers is substantial.

Their stock price is back down to reasonable levels.

Perhaps they'll remain a niche player in the market?

Cloudflare can move into the storage and compute market without changing their business model. Whereas AWS/GCP/Azure cannot suddenly reduce bandwidth prices or offer unmetered networking packages, because their business model depends on using bandwidth pricing to extract high margins.

From a practical perspective, as a developer building an app, Cloudflare has a lot to offer that the other clouds do not. Their new services are developer-friendly, built around modern ideals, and run on a global network. For certain workloads there is a clear argument in favor of choosing Cloudflare over one of the “big three.”

Yes, I see the stock is down. It reminds me of 2015 when AWS was still part of Amazon, and any developer could clearly see that the entire industry was using AWS. And yet Morgan Stanley published 30 page PDF analyses of Amazon’s business without a single mention of AWS. That’s when I learned that Wall Street investors don’t know wtf they’re talking about, which makes sense if you’ve ever met one. Cloudflare looks like a good buy to me.

    #!/bin/sh

    set -e

    if [ -n "$VERBOSE" ]; then
      set -x
    fi

    if [ "$1" = "--show" ] && [ $2 = "twitter" ]; then
      echo "https://twitter.com/teaxyz_"
    elif [ -n "$1" ]; then
      # Hi, I know you’re excited but genuinely, pls wait for release
      # I added this so I can do CI :/
      case $(uname) in
        Darwin) suffix=macOS-aarch64;;
        Linux)  suffix=linux-x86-64;;
        *)
          echo "unsupported OS or architecture" >&2
          exit 1;;
      esac

      if [ "$1" = "brew" ]; then
        d="$HOME"/.tea/bin
        mkdir -p "$d"
        curl https://tea.xyz/dist/tea-$suffix -o "$d"/tea
        echo "$d" >> $GITHUB_PATH
      else
        mkdir opt
        curl https://tea.xyz/dist/tea-$suffix -o ./opt/tea
        chmod u+x ./opt/tea
        shift
        ./opt/tea "$@"
      fi
    else
      echo
      echo "418 I’m a teapot"
      echo
      echo "thanks for your interest in tea."
      echo "alas, we’re not quite ready to serve you yet."
      echo
      echo "while you wait why not follow us on Twitter:"
      echo
      echo '    open $(sh <(curl tea.xyz) --show twitter)'
      echo
    fi

Same for the linux build https://tea.xyz/dist/tea-linux-x86-64

According to an internal message I saw, their monitoring stuff is fucked too.