Love this tool! Discovered it just before the lockdown started and have used it as a collaboration tool in 100+ software engineering interviews since then.
>> How to control access to data (multi-tenancy where there are ~100K tenants)
So basically, you need to run a web server that serves a search page in which your users can create and submit queries. The web server receives the query and then routes it to the appropriate search handler. The web server should handle access control and there are several standard different approaches for this.
Solr and ElasticSearch can both be used in this manner.
>> Database design - Indexes and Shards and best practices around mixing different types of documents in a single index.
Depends a lot on what your users want to get in their search results. A first step would be to identify the primary text fields they want to search in each document type, then create a standard text field in the schema into which each document's primary content gets indexed. You can get fancy by running different document types through different analyzer/tokenizer chains (for example if they were in different languages) and you can do a lot of 'cheating/preprocessing' here so that the primary search text field has good information in it.
Postman allows me to design and mock APIs by simply adding my request and saving the example responses I would like my endpoints to return. The request/response format is what is natural to a web developer and does not need learning another DDL like RAML or OpenAPI/Swagger.
The mock url generated can be directly consumed by anyone without needing any local setup and allows decoupling the consumers of the API from the service deployment allowing parallel development tracks i.e being agile. The documentation comes out of the box when you create anything in Postman and can be shared with your API consumers.
I can then use the same Postman Collection to debug and test my APIs and eventually make it a part of my CI/CD process using their Newman CLI tool or just creating a Postman monitor which runs the API specification with tests on a pre defined schedule and notifies you when the tests fail or experience latency issues in production.
Carbon Clean Solutions built a plant in Tuticorin in southern India that captures carbon dioxide from its coal-fired boiler and converts it into soda ash (a chemical cousin of the baking soda you buy in a grocery store). And, in what Sharma says is a world’s first, the commercial-scale plant set to capture 60,000 tons of CO2 annually does it so cheaply that it did not need any government subsidies.
Before Carbon Clean Solutions came along, the Tuticorin chemicals plant used to buy carbon dioxide to make its soda ash. It also bought coal to fire up its boiler. Now, instead of wasting carbon dioxide that burning coal produced, the plant is capturing it and saving the money on buying any more carbon dioxide. As a plus, the CO2 supply is also more reliable than before.
“I am a businessman,” Ramachandran Gopalan, the managing director of the Tuticorin plant, told the BBC. “I never thought about saving the planet. I needed a reliable stream of CO2, and this was the best way of getting it.”
Postman only has a v1 and v2 data format. No proprietary format. The formats and the SDKs [1] to use them are also open source. The transformer for converting between versions is also open source [2]. Importing works fine for me. You could leave an issue on Github if you found a bug while importing.
Looking forward to this!