We at Moesif (https://www.moesif.com/solutions/track-third-party-api) released a similar tool in 2017 and found that many of our customers including Deloitte, UPS, Snap Kitchen, iFit, and Trung's previous company, Snap Kitchen were looking for a way to track APIs without the complexity of a full service mesh like Envoy. Especially if you're hosted in something that cannot run an on-prem service mesh or gateway.
We're a little different in that we also support agent-based rather than just proxy. Meaning we have an SDK that sits out-of-band.
I prefer REST especially for public/external APIs. It's more empathetic towards third party developers who may not be as intimate with your API as your internal team. For example, much easier to reason a few well-understood entities like items, users, and orders if I was building an e-commerce API then a list of RPC operations. I would add GraphQL can also be easier to understand as long as the entity relations make sense. Lot's of exciting stuff happening in the GraphQL world but it does have disadvantages also.
Interesting to switch away from a static generator due to reliability. We used Tumblr for our first start up since many non-technical folks were writing content (It was a consumer app). We had a bad experience with it being slow loading for users while being very constrained regarding the theming and clunky editor.
Our current startup is much more dev focused (API analytics) so we went with Jekyll and absolutely love it. Just code in Markdown and your favorite editor and host on GH pages. It's free and super fast. No need to worry about theme settings everything is version controlled. These days, even if you need dynamic content like search, you can use Algolia or Lunr if the index is small.
I guess once you hit a point where you have a large team writing and scheduling content to be posted, static generators may not scale well accordingly (and Ghost will prob be one of my first picks), but we love it for smallish dev focused teams.
- Passionate about the API economy and serverless computing
- Experience working on modern backend systems and frameworks using languages such as Scala (preferred), Java, and functional languages
- Experience working with large installations of Cassandra, HBase, ElasticSearch, or similar
- Familiarity with Spark, Storm, Kafka, MLlib, Docker, and other open source technologies
- Building highly scalable REST APIs and data processing pipelines.
Helpful skills:
- Experience working in a modern cloud provider like AWS, Azure, or Google Cloud
- Familiarity with current APM and logging tools like New Relic, Sumo Logic, or Splunk and mobile analytics tools like Mixpanel/Amplitude (Our customers call us the "Mixpanel for APIs")
- An eye for ensuring secure systems
- Awesome at the Unix/Linux command line.
Moesif is a VC backed API analytics and monitoring service founded by MIT and Michigan engineers with deep expertise from Intel/Microsoft/Zynga.
Second Hubspot, great for SaaS companies that focus on inbound marketing. The CRM product is free. If you're a startup, they have a program to get 90% off their other products.
Whatever CRM you use, look for one that integrates with any customer related tools that you're using. Larger players like Hubspot can attract more developer integrations. For example, we use Drift (Like Intercom but much cheaper) for customer support and sync events in Drift to Hubspot.
They seem to be in a unique position to monetize with multiple models. Compared to something like Github, Docker and Docker Swarm has much more opportunity for large enterprise support contracts. Most companies feel that Docker is synonymous with containers, yet still don't fully understand the technology. Git already had a high adoption years before Github was around so developers were familiar with it (or other VCS) and didn't need to spend thousands of dollars to support a git repo.
On the other hand, curious how much revenue DockerHub is bringing in and where they will plan on taking it. That model seems closer to Github. Will it be a newer way to discover new OS or even propriety images like how devs use Github?
They seem to be in a unique position to monetize with multiple models. Compared to something like Github, Docker and Docker Swarm has much more opportunity for large enterprise support contracts. Most companies feel that Docker is synonymous with containers, yet still don't fully understand the technology. Git already had a high adoption years before Github was around so developers were familiar with it (or other VCS) and didn't need to spend thousands of dollars to support a git repo.
On the other hand, curious how much revenue DockerHub is bringing in and where they will plan on taking it. That model seems closer to Github. Will it be a newer way to discover new OS or even propriety images like how devs use Github?
I like to always try to automate stuff as much as possible to remove human error. It's easy to forget an arg or other parameter on a script or even know what the arg was for in the first place. Sounds like their last backup was 24 hrs ago. Having backups are like having good security, you don't realize how important they are until it's too late. Reminds me of this old meme:
It's definitly interesting to see them move. Google already has Google Analytics/Firebase Analytics which pretty much every app developer integrates given their generous free tier so the extra data seems to be diminishing returns for Google. Seems to be more of a loss for Twitter than Google's gain given now they won't have a GA like equivalent.
I don't think Fabric was ever used for Twitter ad targeting just by reading their TOS unlike the Google/FB world and their analytics products but I could be wrong. Seems like a case where Twitter didn't realize the full potential of Crashlytics and Answers.
The economies change a lot when you can book that revenue up front. Many SaaS startups want to lock in year long contracts even if the total amount is less for this reason. That revenue can then be used to pay salaries, etc. Not everything has to be or should be paid by VC dollars.
Nest may have figured they could build a larger ecosystem in the IoT and Smart Home space and charge monthly at some later point but didn't materialize.
We have multiple roles open in San Francisco and remote:
Senior Software Engineer https://apply.workable.com/moesif/j/86483B715B/
Enterprise Sales Development Representative https://apply.workable.com/moesif/j/5E13A09868/