versioning

I have an API written in thrift. Example: service Api { void invoke() } It does something. I want to change the behavior to do something else but still keep the old behavior for clients that expect the old behavior. What's the best practice to handle a new API version? Soft versioning Thrift supports soft versioning, so it is perfectly valid to do a version 2 of your service which looks like this: service Api { void invoke(1: string optional_arg1, 2: i32 optional_arg2) throws (1: MyError e) i32 number_of_invokes() } Since the newly added arguments are technically optional, an arbitrary clients

We're implementing a New system using Java/Spring/Hibernate on PostgreSQL. This system needs to make a copy of Every Record as soon as a modification/deletion is done on the record(s) in the Tables(s). Later, the Audit Table(s) will be queried by Reports to display the data to the users. I was planning to implement this auditing/versioning feature by having a trigger on the table(s) which would make a copy of the modified row(deleted row) "TO" a TABLE called ENTITY_VERSIONS which would have about 20 columns called col1, col2, col3, col4, etc which would store the columns from the above Table(s

I am finding any maven plugin for versioning database changes. There are a few plugins that offer some support for this task: Maven LiquiBase Plugin Maven Database Migration Plugin DbMaintain Maven Plugin (a plugin for DbMaintain , the famous tool from Unitils) I don't have much experience with them, we currently use a custom tool to apply our change scripts. But the Maven Database Migration Plugin is a serious candidate to replace it. LiquiBase is pretty famous but also different, changes are described in a generic XML format. About DbMaintain, it works well (in Unitils) but I've never tested

I'm trying to implement both Attribute Routing and the VersionedRoute from RoutingConstaints Sample but when I use both on a controller, the versioned attribute no longer works. What would I need to modify on the attribute to get it to play nice with Attribute Routing? For code example download the sample project (or just look at the few files from the above link) and then modify the routes as such: // When I use the RoutePrefix, VersionedRoute no longer works (Sending "Api-Version" through http header doesn't route correctly // If I remove the RoutePrefix I can use VersionedRoute again //

I want to use Xcode 9 to add iOS 11 code to my project while keeping the option to compile the project with Xcode 8 which only supports iOS 10. In Objective-C I can do this by using a preprocessor directive to check if __IPHONE_11_0 is defined. Which will hide the code if I'm compiling with a Base SDK earlier than iOS 11. Like this: #ifdef __IPHONE_11_0 if (@available(iOS 11.0, *)) { self.navigationController.navigationBar.prefersLargeTitles = YES; } #endif Is there a way to do that in Swift? if #available(iOS 11.0, *) doesn't work because that's a runtime check. The iOS 11 SDK comes with