id	author	title	date	pages	extension	mime	words	sentences	flesch	summary	cache	txt
blog-twitter-com-7472		Rebuilding Twitter’s public API			.html	text/html	1734	241	69	While the microservices approach enabled increased development speeds at first, it also resulted in a scattered and disjointed Twitter API as independent teams designed and built endpoints for their specific use cases with little coordination. Abstraction: Enable Twitter engineers building the Twitter API to focus on querying, mutating, or subscribing to only the data they care about, without needing to worry about the infrastructure and operations of running a production HTTP service. With the above goals in mind, we've built a common platform to host all of our new Twitter API endpoints. https://api.twitter.com/2/tweets/search/recent?query=%23DogsofTwitter Additionally, if an endpoint can be constructed from queries for already existing data in the GraphQL schema, or if they're able to implement their logic in StratoQL, then we can not only bypass almost all "service owning" responsibilities but also deliver faster access to new Twitter features!	./cache/blog-twitter-com-7472.html	./txt/blog-twitter-com-7472.txt