This post has been imported from my previous blog. I did my best to parse XML properly, but it might have some errors.
If you find one, send a Pull Request.
Due to various reasons including some NDA stuff that I cannot share and after lots of thinking about the way I could push Sewing Machine further, it looks that this project won’t receive much more attention from me. Just to get it clear, this is not related to any “I don’t have time for OSS now” or “omg, nobody likes my project”. It’s simple calculations followed by a few discussions about directions where this project could head.
The nature hates vacuum and at the same time when claiming that SewingMachine is al most dead, I want to bring Lockstitch to the table. It’s again about Service Fabric, it’s again about performance, it’s again about distributed systems done right. Only better and on a different level. Lockstitch is aiming to work with the lowest fabric component, called replicator. The overall goals, as I mentioned are the same.
Interested in learning more about topics like this? Click here to join my newsletter. No spam. Meaningful content only.
If you want to see the where is it heading, a list of issues should provide you all the needed information.
It’s important to mention Tomasz Masternak, who is a co-author of Lockstitch.
Good ideas, don’t die, they reappear in a different shape. This is why Lockstitch could be treated as SewingMachine++.