History spirals. This is an objective process, repeated over and over again. You can regret for the lost time and to mourn about the past greatness, but the facts remain above this - Russia is rapidly losing its status as a leading space power. For more than twenty years, the country does not produce anything new in principle, continuing to exploit the legacy of the Soviet Union. Only lead the modernization of the old backlog, but otherwise everything is just words on paper and projects. Sure, notable past will allow to stay afloat even a decade or two in the role of a space cab, but only as long as the Chinese missiles are not overstep its proper boundary changes and hurl prices on the conclusion of cargo into orbit. From Space romance gone, leaving her only dry figures of financial statistics. Why spend billions on the space, if it does not bring profit for the foreseeable future? In times of confrontation of political systems, the race between the two superpowers has a beneficial effect on the scientific and technical progress. The possible use of military and ideological gave rise to dozens of various projects. Yes, most of them did not go beyond the drawings and models, but the ones that leaked through the sieve test and commissions received unlimited support. The future of the Soviet reusable orbiters not been predetermined even before birth. Despite the huge financial loss ratio of such starts, they can hold out for long on the world stage, giving the vector for future horizons. And to finish my article I want to play on the title and epigraph. Rise My God! From ashes rise! Awake, my God! Rise from the ashes!
If yes, would you share how you got inside? What arrangements were needed? I am curious!
Also, thank you for these pictures. Despite what happens politically (projects die, or supported to success), it is inspiring to think about how many people worked on this project. All that effort... as it is now. :(
It is only fair their work gets viewed and known!
PS: I assume English is not your first language. Hopefully my sentences were understandable. Your English is still much better than my (zero) Russian (assuming). :)
PPS: Before someone mentions it, yes, I am aware there were charges thrown around of technology copying in the Buran program. Whether or not those have any truth, they obviously weren't handed "shuttle in a box" plans. Imho, it's still nice to appreciate all the work that was put into something that never flew into space.*
Putin just cut the space program by a third. Russia is becoming a bit player in space and has no ability to compete with what NASA, SpaceX, and Boeing are building now. The Soyuz work-mule as a LEO transport is pretty much it for them for the forseeable future and with the ISS retirement, it won't have anywhere to go.
I suspect there are lots of people who built applications on top of MongoDB who would like to transition away from Mongo onto a different database, or would at least like the option to be able to to. This may provide a good mechanism for a transition.
Which leads to a question for the OP: does this work with mongoose.js?
i started a mongo client implementation in node.js, but it fell off my radar - the goal was to get it to work with mongoose, etc: https://github.com/JerrySievert/mongolike-client (it is not yet complete).
in the end, i just wrote my own database system, with a query language that could act as an intermediary from multiple sources (SQL, mongo, etc).
but, this stuff is mostly just for fun, my day job keeps me plenty busy.
problem : meteor relies on a specific mongodb feature,ie polling the db for any change. I heard there is experimental support for PG but it seems to rely on a complex hack using triggers ... So the issue isn't really about mongo queries, but whether it is possible to track db edits from third parties or not.
That specific MongoDB feature is "tailing the oplog", where the oplog is the capped collection with the idempotent commands that represent the changes in the database. This is what Meteor uses to receive (be pushed) changes (not polling).
Certainly, logical decoding provides the necessary infrastructure to implement it (and also normal tailable cursors): thank you Andres, really nice work! :) But some work is also needed to transform the representation you are using in PostgreSQL into MongoDB's oplog entries.
This is definitely what we are using in ToroDB to emulate it (currently, under development).
