Mobile Monitoring Solutions

Close this search box.

Couchbase Updates Mobile And Edge Support – I Programmer

MMS Founder

Posted on nosqlgooglealerts. Visit nosqlgooglealerts

Couchbase has released Couchbase Mobile 3, which the developers say includes many enhancements to the Couchbase Lite and Sync Gateway products for mobile and edge computing solutions.

Couchbase is a distributed NoSQL cloud database that grew from a merger between Membase and CouchOne, with the aim of creating a scalable, high-performance document-oriented database system. Couchbase combines the properties of a distributed document database (JSON) with features of a traditional DBMS including distributed SQL, transactions, and ACID guarantees.


The headline changes to this major release start with the addition of a C API for Couchbase Lite. The new API means developers can use Couchbase Lite on a variety of embedded platforms. The Couchbase team says they are also introducing “significant architectural enhancements” that will make it simpler to configure and administer the platform.


Specifically, the Sync Gateway configuration has been improved to make it cluster-aware, and it now provides a secure RESTful API endpoint to make runtime administration simpler. The API also has support for database encryption in the form of client side field level encryption. This means Couchbase Lite C clients can encrypt fields in documents before it is replicated to Couchbase Server..

Query support has been extended using a fluent API that in addition to supporting SQL can now be used with N1QL formatted query strings. N1QL for Mobile is Couchbase’s implementation of the SQL++ SQL-for-JSON query language specification.

Kotlin support has also been improved in this release. Untill now, Android app developers had to make use of Kotlin’s interoperability with Java and use the Android Java SDK for Couchbase Lite within Kotlin apps. This release comes with a “fully-supported, out-of-the-box idiomatic API for Kotlin” that avoids the need for custom extensions.

Couchbase Mobile 3 is available now. 


More Information

Couchbase Website

Related Articles

Couchbase 7 Adds Relational Support Model

Insights From Couchbase Connect

Couchbase Connect Goes Online

Couchbase Launches JSON Analytics

Couchbase Mobile Version Adds Sync Gateway

Couchbase Server 4.0 Now With N1QL

What Happens To Couchbase Now?

Couchbase Server 2.0


To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin.




or email your comment to:

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

GitLens 12 Brings Support for Visual Studio Code for the Web

MMS Founder
MMS Sergio De Simone

Article originally posted on InfoQ. Visit InfoQ

GitKraken launched GitLens 12, an open-source Visual Studio Code extension that enables to use Git from Visual Studio Code for the Web and Besides new free features, improvements, and fixes, GitLens 12 also introduces premium features, including Worktrees and Visual File History.

GitLens 12 is one of the first extension for Visual Studio Code that gets ported to the Web version. As we noted at the moment of its announcement, Visual Studio Code for the Web cannot automatically use all extensions that run in Visual Studio Code for the desktop. This is mostly related to the impossibility or running the Node.js API or loading modules. In order to support the Web, GitKraken had to completely refactor GitLens internals by introducing a Git provider model able to work in the different environments.

According to GitKraken, support for Visual Studio Code for the Web means developers can have the same experience when accessing Git repos when using a desktop computer, a tablet, or a browser, including insights to understand why things changed, when, and by whom. GitLens is highly customizable.

GitLens 12 also introduces a number of new or improved features and fixes. New features include a new Home View including welcome content, help resources, and so on; the possibility of quickly see all issues fixed in a release; the ability to choose a stash when opening or comparing file revisions, and more.

The two most compelling new features in GitLens 12, Worktrees and Visual File History, though, are available exclusively under the new premium model. This means premium features requires having a user account, which can be free for public repos, and must be a paid account for private repos.

The Visual File History makes it possible to inspect the evolution of a file with all the relevant details, such as changes, their size and authors, etc. Worktrees is a feature that aims to simplify developers’ life by enabling checking out multiple branches at once, with each working tree opened in its own window or all together in the same workspace.

GitLens 12 can be installed from the Visual Studio Code marketplace.

GitKraken is also maker of a popular desktop Git client that is available for free to solo developers and under a paid model for companies and enterprises.

About the Author

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

Presentation: Building with Extensibility

MMS Founder
MMS Christi Schneider

Article originally posted on InfoQ. Visit InfoQ


Schneider: I’m Christi Schneider. I am a software engineer at Square. I’m going to talk to you about building extensible software. This will be high level. We’ll talk about building software from the ground up. The power points you should be thinking about extensibility, and how to plan to make your software extensible.

What is Extensibility in Software?

Let’s start with the basics. What is extensibility in software? Basically, it is the ability to extend out of the box functionality. You have some product that you build, and you’d like partners to play in your ecosystem. You want them to be able to use your data or show their data in your software. This often requires a partner ecosystem. You can see here, a screenshot of the Square developer site where you can go to find documentation and APIs that work with the Square platform. You may not realize it if you haven’t talked about the concept of extensibility, specifically, but most software engineers have extended some piece of software during their careers. It’s pretty rare that you’ll be working on completely standalone software that doesn’t integrate with any other systems.

When to Consider Extensibility in the Software Build

When should you be thinking about extensibility when you’re building software? This shouldn’t be an afterthought. A lot of the things you might think of as checklist items, like the things I’ve mentioned here are often thought of towards the end. When you say, no, I need internationalization so that this can be used in more than just the U.S. Those things that really touch many parts of the system for the extensibility can really be difficult to finish at the end of your project. You really should be thinking about all of these from the beginning.

You might have heard the term mobile-first or API-first. This is used by people who have experienced an issue in the past, like they suddenly needed to make a non-mobile website, mobile. They say what we really should have done here was we should have planned for mobile at the beginning, so next time, we’re going to build something, we’re going to do it mobile-first. This is a fallacy. All of these things are things that you need to be thinking about throughout the design and implementation of what you’re building. Really, no piece of the software is more important than any other piece. You need to do all of these things. Some of them are more important than others, but you should be at least thinking about them at every point during the software lifecycle.


Let’s talk through some examples. This really basic one is interfaces and abstract classes. This is a very basic concept of object oriented programming. Here, you’ve got a Java example of an InputStream, the basic shape of an InputStream, you read, and flush, and close. Each of those implementations might have a different way of doing each of those things. Google Chrome extensions. These extensions can be installed on top of your Chrome browser and do things within websites you visit. Social media share buttons are a type of extensibility. This is taken from the sessions page on the QCon website. Here, you’ve got buttons that let you share to Twitter or Facebook, and those will open a modal or open the website that will let you create a tweet or a Facebook post. Those are both provided by Twitter and Facebook as part of their API in order to extend their websites. A Myspace profile page from 2008. This is Lana Del Rey’s old Myspace. Here you can see a music player that’s embedded. This is a Flash Player. There are lots of different things you could embed in your Myspace page and customize. Then you have iPhone and Android apps. You might not think of this as extensibility, but it really is. On an iPhone, Apple has a platform for developers to grade apps that tie into the phone’s hardware. Basically, any app that you install is extending the functionality of your phone beyond its out of box functionality. Voice skills. All of the skills that you can write and add to your voice assistants are extensions. They do lots of things like tell you what the weather is, for example, that you can install applications just like you can on a phone that extend the functionality of that device.

Levels of Extensibility

Let’s imagine another very common scenario where somebody who maybe works in an office has to download a CSV from one piece of software and upload it into another piece of software, and they have to do this every day. This is all manual. They literally go and click download. They download a CSV file. They go to the other place, and they click upload and upload that file. That’s processed by the second system, and something happens with that data. The way that extensibility can help a little bit here, let’s imagine that we get an IT intern for the summer. The office manager says, “I have to do this thing every day. It takes up all my time. Could you help me make this better?” That IT intern would add a button that pushes that CSV file from one system to the other. Instead of the office manager having to go into both websites every day and download and upload, they just have to click a button.

The next level, you might get some automation. Maybe this happens on a nightly process. All of these things are ways to make the office manager’s life better, but it’s really still not perfect. There’s lag time between when the data comes into system A and shows up in system B. Other than that, might be to use webhooks, and whenever an event occurs in system A like a record is added or updated, then some process picks up that change immediately and puts it into system B. If system A or system B were very extensible, you might not even need to go log into both of them. What this could look like is rather than having to log into system A to track one thing or system B to track another thing, you might just go to system A and it shows the information from system B, or vice versa. You no longer have to use two systems, you can just use one, even though the data is actually coming from both of them. In this case, you might also use that webhooks example to get the data from one system to the other as far as your extensibility in addition to webhooks. Maybe you don’t really need to go log into both systems, and you can just go to one place to manage everything you do.

Types of Extensibility

We can talk about the different types of extensibility. There’s actually two different kinds of data model extensibility. First, you can have an entirely new data model. Let’s say I have this data model. These partners have the ability to add new data models, those could be supported in some cases, or data models that conform to a specific shape. Then you have fields on data models. In this case, these two properties, salesforce_id and is_awesome are coming from other systems. Things you need to consider here are how you’re actually going to represent this in your database. How are you going to deal with daemon conflict? What if you want to add an is_awesome flag in the future, are you going to break everybody’s data that is already set up within this awesome flag? Is it going to conflict and overwrite all those values? That’s something you need to think about before you release publicly. If you’re going to add the ability to make custom fields on a data model, you do need to think about how those will actually be managed. You have API extensibility. I’m sure all of you have used an API at some point. This is a screenshot of the Square Payments API. Very often this is going to be a REST API with CRUD operations.

Then there’s UI extensibility. This is a screenshot of the QCon Plus website. Here you can see they’ve embedded a live feed of tweets that tag QCon. This is something provided by Twitter, where you can embed a feed, then it will automatically pull tweets onto your page, and they still update live. That was having another system’s data show up on your website. The other way is having your data show up on that first party website. This is from a Salesforce tutorial called Recipes. This shows you how to create UI inside of Salesforce. This Hello tab is entirely custom. You could build out a, for example, Square tab that has Square information that would allow someone who’s using Salesforce as their system of record, to not have to leave Salesforce in order to do everything they need to do for their jobs.

Another type of extensibility is event streams. A very common implementation is webhooks, where your system will subscribe to events in another system that you want to be updated about when that event occurs in that other system. They will call an endpoint that you own and that let you know that something has happened. Then you can trigger a process based on that. Event streams are less common, but are used in some particular use cases. Event streams, you generally need like a live connection for, whereas webhooks can be asynchronous. You could use serverless architecture for webhooks, whereas you couldn’t for event streams.

Other Considerations

There’s a lot of things that you need to consider when thinking about extensibility in your product. A big one is backwards compatibility. Once you have a public API, or you have something public that anybody is using, it’s a faux pas to break existing integrations. I’m sure many of you have encountered backwards breaking changes in APIs or libraries that you’re using. You know how it can cause issues. You also want to make it not super difficult for you to upgrade. You want to add tests so that you’ll know if you broke backwards compatibility. You’ll want to make it so it’s not a huge process every time you want to upgrade, and that you really don’t have to think about it if possible. Try not to paint yourself into a corner. Similarly, maintainability. If you have this public platform, you need to keep it up to date. You need to think about when new software comes out, for example GraphQL, if you’re going to go implement new things in that. Often, this gets forgotten about by product managers, because it’s not that visible. People can’t just go click around in it necessarily. Any APIs, security is a major consideration. You also don’t want nefarious users to be able to take advantage of something that you’re providing in order to make better software for your customers, which is really the end goal of all of this.

You need to know pricing. Is it going to be free to use your API? If not, what is going to be people who want to use it versus just not using it versus going to a competitor? If you do make it free, how are you going to get it to pay for itself? This isn’t necessarily something that engineers need to be doing like a business analysis for, but it is something you should make sure to talk about with your team. Just consider at the beginning, especially if you’re like a lead engineer or an architect, if your product manager hasn’t mentioned how this will make money. That’s something to bring up and ask about.

Privacy, it’s similar to security, but you need to think about if you’re storing PII in your fields, or you’re allowing partners to enter PII. How you’re treating that data, if it’s getting exposed where it shouldn’t be, or clogged, or anything. Just like any first party data, you also need to be careful with third party data. If those third parties get any data that has PII in it, something you might need to think about here is how it will work when you get a data deletion request. If I contact you, and I say I want you to delete me. I want you to delete all the data associated with me, and you do that, does that mean that any data that your partners have pulled previously is also deleted? If not, do I know that I need to go talk to them? Are you going to go talk to them? How do we make sure that my data isn’t somewhere that I don’t know about, and that I don’t expect it to be? Reporting is a hard thing in software in general. It’s even harder when you think about third party data.

Reporting is both ways here. Can you use some third party reporting software for your first party data? Say I want to view my data in Tableau, can I pull that data out and visualize it? Then for third party data, does their data show up in your first party reports, or can it be included optionally. Say, there’s some third party integration that has a field that is extremely important to one vertical that’s not included in the first parties, but that’s something that basically all customers in that vertical need on all of their reports. Is it possible for that to show up, or will that third party that includes that field for them, need to recreate all of your reports, but just with this one extra field added?

How will you support this API? If something goes wrong with any of the platform that you build, that is publicly available, how will that be supported? Do you have the support people that you need, and are they trained properly in order to support this platform versus that they see an error message on a website? Additionally, if you have third party integrations that are showing up in your system, how will support determine if the problem is in your system or in that third party system, and direct people to the appropriate place. Something that would be pretty bad is if there’s a major issue, like a very important page fails to load site, and the customer is trying to access that. Calls your support. Your support goes back and forth with them finally saying, “It’s this third party integration. You need to call them.” You really should think about how that interaction will work ahead of time. Try to minimize that back and forth, and then redirecting them, saying, it’s not our fault. It’s not really a great customer experience. Just consider those when you’re talking to support, when you’re figuring out a support plan for your platform.

Developer support is also a consideration if you have a public platform. You’re going to need to have a way for developers to see the documentation for your platform, and find out how to use your system. Very often there will be developer forums, or idea banks, or bug filing systems like Jira. Tying into that, there’s the partner ecosystem apps or any tools that developers might use to interact with your platform. The better these are, the happier your developers are going to be. If you have a very mature partner ecosystem and a very good app store, that’s going to make people more likely to use your platform. If they’re missing some of these tools, or they’re just not as good as they could be, that will make people not want to use your platform. You can also consider no code or low code integrations. Think about things like, if this, then that, where you don’t need to write any code in order to tie into an API.

Something that people often don’t consider until later is that the extensibility you’re building for third parties might enable your first party developers to ship functionality faster and easier. A lot of companies, they basically want first parties and third parties to build things in the same way. One of the companies I worked at, custom code was built in exactly the same way as first party code. All the tools that we use internally, we would also provide in our SDK. This meant that all of the tools that our third parties were able to use were pretty good, because they were the ones that we needed the T’s to do our jobs. This is one way to do dogfooding, where as soon as you build these tools, you have testers built in. If there’s ever a time where a first party developer needs to Slack message you to ask how to use something, or if they need to go read code that’s not open source, that’s a potential problem and should be addressed in your documentation.

Software Lifecycle

When should you think about extensibility? As I’ve been saying, extensibility along with all the other checklist items that I mentioned earlier, are really things that you need to think about throughout the software lifecycle. Discovery and requirements gathering. When you’re first gathering the requirements for your software, and talking to your potential customers that you should also be talking to the potential partners. What are the other pieces of software that those potential customers use? Is there a leader throughout that industry? Do they have an API? How do they play in the partner ecosystem? Can you establish a partnership with them early on? How can you integrate your systems together? Are there any parts that are very important to a particular vertical that you know you’re not going to be able to build for that you’re expecting a partner to build for? Are you enabling partners to build for that? Do you have an ecosystem that partners will want to build on? Can you find a partner to build up that piece so that you are unable to build fully?

When you’re designing and architecting your system, you need to think about extensibility there, both UI design and architectural design, of course. In UI design you need to think about if third parties are going to be able to add elements to your UI, how will that show? Then, when architecting your system, if you are building something like the Facebook event feed. If that feed is architected to only pull from an internal database that has five different event types in it, how is that going to work if you want some other event types to show up in there? If you want to integrate with Ticketmaster and have Ticketmaster events show in your timeline. Are they going to be able to add those events straight to your database, or do you want to consider a different architecture that better supports pulling from multiple sources, as long as they follow the same shape. When you’re writing the code that your partners will tie in to, making sure that you’re doing the same due diligence you do with your UI components, as you do with your developer platform.

When you release, you need to consider how you’re going to release changes to the developer platform. How do you get news out to your developers that are working on your platform? When you release, are your third party developers ready for this? How do they know when a release is coming, or what was changed in the release? Do you need to release a new version of your API and have an upgrade plan? Does everyone get over-the-air updates? Do your APIs match with a specific version of the software that’s installed on user machines where some calls will only work on certain versions of the software? Then, iteration, often forgotten in software. You do need to iterate on your releases. You need to gather feedback from your users, in this case, other developers, and see if any changes are needed. See if there are any bugs that you need to fix. See if there’s something that people really want that you’re not supporting today. Then go back and actually implement those changes.

Dog Adoption Exercise – Requirements

We’re going to go through an exercise in extensibility. We’re going to talk about how you might build a dog adoption website. Your first requirement, obviously, is that potential adopters can view your adoptable dogs. They’re going to want to filter on things like location, and size, and breed. You need to get those dogs in there somehow. Another major requirement is that shelters can list their adoptable dogs. They can fill in all that information that people want to filter on, as well as uploading photos, adding a story, and recording how much it’s going to cost to adopt that dog. Then they will want to be able to mark the dog as adopted. These shelters may want some type of analytics. They may want to see which dogs are getting a lot of clicks, which dogs get the shortest time to application or a completed adoption, and maybe drive their behavior based on those analytics so that they can get dogs adopted more quickly.

Dog Adoption Exercise – Extensibility

With this dog adoption website, it’s pretty basic right now, there are some ways that this could be extended, so that more functionality is available for your website. Maybe some people want to, in their news every morning, hear about new adoptable dogs near them, cat adoption. If you’re building software that lets you list and adopt dogs, it seems like it’d be relatively straightforward to allow other types of animals on this platform. If you didn’t consider that other types of animals might be available at some point when you began building the software, this might be really hard to retrofit later. That could be something you’d want to think about from the beginning and build it out so that it’s generic, so that you have this animal shape with cat or dog specific fields in a child object or in a related table, or something like that. You might want to be able to show DNA test results on your dog data model through your API and on a webpage. If there are any rescues that do DNA testing, they might want to just be able to embed this nice, beautiful UI into the dog’s web page so that that’s visible to anyone who’s trying to look at dogs. Maybe this could automatically tie into that breed data that I mentioned earlier. Where as soon as the dog’s DNA test results come back, it updates the dog data to replace all the breeds that were on the dog’s data before with the breeds from the DNA test results, so that people who are looking for particular breeds can find dogs that would be a good match for them.

A lot of dog fosters will create an Instagram account, or a hashtag for the dogs they’re fostering in order to help get them adopted. You might want to embed an Instagram feed for a particular account or hashtag on the dog’s webpage. This will let potential adopters see the dog as they live and play throughout the day. You might want to trigger an event to occur when something happens in your system. In this case, when a dog is adopted, make a Facebook post. You can also do things like integrate with Apple Pay to pay for adoption fees. There are lots of different payment integrations out there, and most of them have some extension that you can embed within your website in order to accept their payment methods. Shelters are always trying to get their animals adopted more quickly, so that they can pick up new animals in order to get those adopted. They might want to do some A/B testing to see what gets their dogs adopted faster. Do dogs with an Instagram feed embedded get adopted more quickly than dogs without one?

Questions and Answers

Betts: There are a lot of concepts, I think people who don’t work with extensibility, or don’t think about it or think it’s something you can apply later on, may not realize just how broad the category is. Is this something that you’ve just started doing at Square, or you’ve been working in this space for a while?

Schneider: Yes, I have been working in this space for a while. I have a lot of industry experience here. I worked on an extensible product for most of my career at my former employer, your current employer, Blackbaud, a couple different products there. That gave me a ton of experience, especially working directly with the developers who worked on the platform and seeing their needs. Then I worked on the extensibility team there and then more recently at Square. Working at Square has been good to see a different perspective, see what things are the same and what things are different. Then I have quite a bit of experience with working with other platforms personally, because I worked on many hackathons. Then, I also worked on the innovation team at Blackbaud as well.

Betts: I know Square is one that a lot of companies interact specifically with their API. They’re there for payments and stuff like that. It’s foundational to the Square business model. I think one of your other examples was Salesforce, which I think is up there as canonical. They exist as a way for people to extend and integrate. In fact, I know more people who work on modules that add on to Salesforce, or I think SharePoint is another one. Most of us aren’t working on a Salesforce or SharePoint. How do you consider this for, we want to start doing some extensibility. How do you get a company that’s much smaller to just get started, or is it something you just put off and delay and come back to later?

Schneider: I think when you look at companies like Salesforce or Square, those considered extensibility in their initial product. They knew they would never be able to build for all the verticals and niche users that they would want to support. They planned for having a great developer platform and attracting partners that could build out those pieces that they can support. I don’t think that is the right decision for many companies. It definitely requires a lot of upfront investment. The things I went over in my presentation are just things you could do. I don’t think every developer platform should have all of those things. I think if I was building out a platform where I thought that I would need extensibility, I’d probably do some market research. Figure out exactly what people are looking for, and just start with that very small, minimal extensibility and build from there. Because you don’t want to make a huge investment on something that people aren’t going to use, and then you’re going to deprecate and the 10 users you did get are going to be very upset and move to a different platform.

Betts: I can see it being one of those tradeoffs, you don’t want to go too far in one direction versus the other. To your dog adoption example, someone says, we should make an app for adopting dogs. The developers probably are going to be like, great, I’ll go create the dog adoption service. Do they think that I should create this pet adoption service, it’s more generic, or is it some anything adoption service? It’s a different way of thinking. Who is involved in making the decision of saying we need to start doing an extensibility first mindset for all of our development and planning?

Schneider: I think it’s really part of everyone on the team’s job to think about that. I think, really, it’s going to fall to the lead developer and architect, if those are different people, to make sure that product management is considering extensibility when they’re writing features for the backlog. If you know that you’re going to need some extensibility but you don’t see that represented in your backlog, you need to speak up and make sure that’s in there. That when you’re writing the technical details for stories, you have written in the parts that enable extensibility.

Betts: A lot of the examples you gave were public facing APIs, app stores, things like that. Is extensibility something you should be thinking about if you’re only developing an internal application?

Schneider: If you’re a very small company, probably not something that you might want to invest the time and money into. If you are a company that has a lot of engineers or thinks they will have an external platform one day, you might want to invest the resources to build out internal APIs and tools that your internal developers can use. Then that will make creating this external developer platform easier in the future, and make it so all your internal APIs follow certain standards. You don’t need to do a ton of work adding documentation or making sure all your endpoints are named the same thing, or whatever.

Betts: I think that’s a good lead into the next session, which is about standards and creating a standardized specifications driven lifecycle. It is, how do you get those standards defined? If you start using them internally, it’s that dogfooding process that all of our developers have to use the API, it makes the API better. You can also start enforcing some rules and some checks and some governance around making sure that all of our APIs across all of our microservices, whatever we’re doing, start looking somewhat the same.

Schneider: With everything in software, it’s always a tradeoff. You don’t want to have everyone spending 10% of their time on fixing dumb little things in their APIs. You also don’t want to have to do a year’s worth of work when you want to make these public.

Betts: Would you consider extensibility the same as plugin capabilities? Is this just a naming convention? Is a plugin just another form of extensibility?

Schneider: Yes, I think so. I think that’s similar to Chrome extensions, and other of the examples I mentioned. Plugins are a type of extensibility. I think the word plugin can mean different things in different places as well. Flash was a plugin for Chrome. I think that plugins are certainly part of extensibility.

Betts: You had a slide that had other considerations that just kept adding on. I think it’s almost daunting. It made me think, accessibility. There’s a few of the other lesser ilities that get thrown on. You’re like, “We don’t have time for that. We’ll come back and put it on later.” Then you realize you didn’t think about it up front, you’re going to run into a big hell of problems. I think just versioning backwards compatibility is probably the thing most people that develop an API run into first if they have customers. What are some of the other ones that you would say you need to be thinking about this before you just say, we’re going to make our product extensible?

Schneider: Probably the main point you should take away from this presentation is that extensibility is not something you can just tack on at the end. You do need to be thinking about lots of things all the way through. A lot of those things are more of a general consideration when architecting something versus something that maybe a junior engineer would do. Which is like, when I’m building out a feature, what are the core requirements for this feature? What buttons need to be where and what needs to happen here? It’s something that you really are thinking about when you’re thinking about higher level of software. The most important, certainly backwards compatibility because if you break backwards compatibility, you’re going to break all of your existing implementations from your partners, and they’re never going to want to work on your platform. Your clients won’t be happy either because their existing integrations that they depend on won’t be working. I think probably the next probably equally important is the developer platform. You have to have a public facing website to explain how to use your platform. You can’t just be like, I don’t know, we have an API.

Betts: Figured out.

Schneider: Yes, basically. There’s many tools you can use to create that, that are very easy to use and do a lot of things out of the box. If you use OpenAPI, there’s a bunch of tools that will consumer your OpenAPI and make it pretty. Even Postman can do that. Take advantage of tooling that’s out there. I think having somebody who is experienced with the tools that are available or knows how to do the research to find what tools would be good for your solution is pretty important.

Betts: Drawing the line, this is if you focus so much on extensibility, do you get too far away from your core features? If you only do your core features, are you making it too hard to implement extensibility later and add it on? The way I interpreted that is, are there things you should watch out for that make it almost impossible to make your product extensible without a complete refactor and redesign?

Schneider: I think we’ve probably all seen software that’s almost impossible to extend without rewriting. I think this is where you see software engineering as an art rather than as a science. There’s no one thing that’s going to make it hard to make something extensible later. It’s something that you’re going to learn over time as you use other APIs and as you build your own. It’s ok to make mistakes. A really good way to make mistakes is to make a beta, and then if you break things, to avoid an upset, so definitely recommend doing alphas and betas if possible.

See more presentations with transcripts

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

NoSQL Market Share 2021 – Industry Research Update, Future Scope, Size Estimation …

MMS Founder

Posted on nosqlgooglealerts. Visit nosqlgooglealerts

Market Research

Global NoSQL Market research is an intelligence report with meticulous efforts undertaken to study the right and valuable information. The data which has been looked upon is done considering both, the existing top players and the upcoming competitors. Business strategies of the key players and the new entering market industries are studied in detail. Well explained SWOT analysis, revenue share and contact information are shared in this report analysis. It also provides market information in terms of development and its capacities. 

MR Accuracy Reports crafted the report, titled Global NoSQL Market 2021 is a methodical research study based on the NoSQL Market , analyzing the competitive framework of the industry in the world. Using efficient analytical tools such as SWOT analysis and Porter’s five forces analysis, the report provides a comprehensive assessment of the NoSQL Market . Our big research team were able to captured all-important chapters in the final report as they have been striving towards it.

Download Free PDF Sample Report with Complete TOC and Figures & Graphs (with covid 19 Impact Analysis):

According toMRA study, over the next 5 years the NoSQL market will register a xx% CAGR in terms of revenue, the global market size will reach xx Million USD by 2026, from xx Million USD in 2020. In particular, It should be noted that the impact of the epidemic has accelerated the trend of localization, regionalization and decentralization of the global industrial chain and supply chain, so it is inevitable to reconstruct the global industrial chain. Faced with the global industrial change in the post epidemic era, enterprises in various countries must take precautions. This report presents revenue, market share and growth rate for each key company. In this analysis report, we will find below details:

1. Full in-depth analysis of the market structure along with forecast from 2021 to 2027 of the various segments of the Global NoSQL market.

2. Who is the leading company in NoSQL market, competitive analysis of key companies, mergers and acquisitions, market dynamics.

3. Which region has become the biggest growth area in NoSQL market?

4. The Most Potential segment in each regional market.

5. Insights about factors affecting the market growth, including the impact of COVID -19.

6. Global NoSQL market based on value chain analysis, and SWOT analysis.

7. Regional market analysis to the current revenue (Million USD) and future prospective.

Major players operating in NoSQL market-Competitive Analysis:

IBM Corporation

Aerospike Inc

MarkLogic Corporation



Oracle Database

Neo technology


Basho Technologies



Regional Segmentation (Value; Revenue, USD Million, 2016 to 2027) of NoSQL Market byMRA include:






Southeast Asia

South America

Type Outlook (Value; Revenue, USD Million, 2016 to 2027):

Key-Value Store

Document Databases

Column Based Stores

Graph Database

Application Outlook (Value; Revenue, USD Million, Market Share, 2016 to 2027):


Online Game Development


Social Network Development

Web Applications Management


For any other requirements, please feel free to contact us and we will provide you customized report.

Get Exclusive Discount on this report:

Key questions answered in the report include:

  • What will be the market size and the growth rate by the end of the forecast period?
  • What are the key Global NoSQL Market trends impacting the growth of the market?
  • What are the potential growth opportunities and threats faced by the leading competitors in the market?
  • What are the key outcomes of Porter’s five forces analysis and the SWOT analysis of the key players functioning in the Global NoSQL Market?
  • This report gives all the information regarding industry Overview, analysis and revenue of this market.
  • What are the market opportunities and threats faced by the vendors in the Global NoSQL Market?

If you have any special requirements, please let us know and we will offer you the report as you want

You can buy the complete report @

About Us:

MR Accuracy Reports’ well-researched inputs that encompass domains ranging from IT to healthcare enable our prized clients to capitalize upon key growth opportunities and shield against credible threats prevalent in the market in the current scenario and those expected in the near future. Our research reports arm our clients with macro-level insights across various key global regions that equip them with a broader perspective to align their strategies to capitalize on lucrative growth opportunities in the market.

Contact Us:
MR Accuracy Reports,
USA: +1 804 500 1224
UK: +44 741841 3666
ASIA: +91 747888728100
Email: [email protected]   

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

NoSQL Database Market Outlook by Key Players, Industry Overview, Supply and …

MMS Founder

Posted on nosqlgooglealerts. Visit nosqlgooglealerts

Functional Food and Beverages Market Research Report

The report on the global NoSQL Database Market provides information on the competitive landscape and strategies for key players and products along with potential and niche segments, geographical regions exhibiting promising growth. The report tries to give a neutral perspective on Market performance and must-have information for players to sustain and enhance their Market footprintIt also offers historical, current, and projected Market size regarding volume and value along with recent industry trends and developments in the NoSQL Database Market. The study not just offers estimations and projections, but also an uncluttered evaluation of these figures on the Market dynamics. These insights merge data-driven research framework with qualitative consultations for business owners, CXOs, policy makers, and investors. The insights will also help their customers overcome their fears.

The government bodies of many countries across the globe are increasing their efforts to contain the spread of COVID-19. Thus, they are offering financial support for various research and development activities related to the coronavirus. Apart from this, many nations have started the COVID-19 vaccination drives.

Download FREE Sample Copy of NoSQL Database Market Report @

Benefits of RMoz Study

RMoz has gradually established itself as one of the leading Market research companies in India. Our unique, methodical, and up-to-date approach towards creating high-quality Market reports ensures the reports include relevant Market insights. Further, our team of analysts leaves no stone unturned while curating Market reports in accord with the requirement of our clients.   

Some of Following Top Market Players Profile Included in This Report: 

  • DynamoDB
  • ObjectLabs Corporation
  • Skyll
  • MarkLogic
  • InfiniteGraph
  • Oracle
  • MapR Technologies
  • he Apache Software Foundation
  • Basho Technologies
  • Aerospike

Get Best Discount On This Report :

Global NoSQL Database Market Segmentation:

The market for NoSQL Database is divided into six major segments which including type, deployment, service, organization, application and region. The study offers a comprehensive analysis of the segmentations in the global NoSQL Database market, this segmentation includes the segments which hold the major contribution into the market and also provides detailed growth parameters about the market.

Market by Type:

  • Column
  • Document
  • Key-value
  • Graph

Market by Application

  • E-Commerce
  • Social Networking
  • Data Analytics
  • Data Storage
  • Others

By Region

  • Asia-Pacific [China, Southeast Asia, India, Japan, Korea, Western Asia]
  • Europe [Germany, UK, France, Italy, Russia, Spain, Netherlands, Turkey, Switzerland]
  • North America [United States, Canada, Mexico]
  • Middle East & Africa [GCC, North Africa, South Africa]
  • South America [Brazil, Argentina, Columbia, Chile, Peru]

The report on the NoSQL Database Market will help readers to:

  • Have a clear understanding of the NoSQL Database Market at present and the possible revenue it can generate during the forecast period.
  • Understand the key drivers, restraints, and challenges of the Market
  • Analyze the consumption pattern and impact of the end use segments on the growth of the NoSQL Database Market
  • Study the NoSQL Database Market in terms of the table of segmentation and list of players
  • Investigate the recent Research and Development performed by various players of the NoSQL Database Market.

Inquire More About This Report @

As the coronavirus disease (COVID-19) crisis takes over the world, we are continuously tracking the changes in the markets, as well as the purchase behaviors of the consumers globally and our estimates about the latest market trends and forecasts are being done after considering the impact of this pandemic.

About ResearchMoz

ResearchMoz is the one stop online destination to find and buy market research reports & Industry Analysis. We fulfil all your research needs spanning across industry verticals with our huge collection of market research reports. We provide our services to all sizes of organisations and across all industry verticals and markets. Our Research Coordinators have in-depth knowledge of reports as well as publishers and will assist you in making an informed decision by giving you unbiased and deep insights on which reports will satisfy your needs at the best price.

For More Information Kindly Contact: 
90 State Street,
Albany NY,
United States – 12207
[email protected]
Media Release:
Follow me on :

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

Shepherd, Guided User Tours of Your Application

MMS Founder
MMS Guy Nesher

Article originally posted on InfoQ. Visit InfoQ

Shepherd is a JavaScript library that provides a simple interface for creating guided user journies in web applications. It’s framework-agnostic, easy to use, and works great on desktop and mobile applications alike.

Guided user journies or product tours are a popular way to onboard new users and help existing users to discover new functionality in applications.

To start a new guided tour using Shaperd, install the library using npm/yarn or grab it directly from the CDN provided in the installation guide and then initialize the tour and add the desired steps to the tour following the example below.

// only needed when installing via npm/yarn
import Shepherd from 'shepherd.js';

const exampleTour = new Shepherd.Tour({
  useModalOverlay: true,
  defaultStepOptions: {
    scrollTo: true

In this example, we add two custom properties during initialization.

useModalOverlay creates a backdrop behind the tour modal and the target element, which makes it much more readable.

scrollTo tells Shepherd to scroll the target element into view when the step is shown.

  id: 'first-step',
  text: 'This is the first step of the tour',
  attachTo: {
    element: '.example-css-selector',
    on: 'bottom'

Once the tour is initialized, the developer adds the individual steps through the addSteps method, passing in an array of steps.

Finally, tour.start() will kick the tour off. Developers should consider adding a setTimeout to avoid triggering the tour immediately.  Developers should also track which guided tours have been displayed to the user in order to avoid displaying them again on every visit.

The defaults used by Shepherd do not take advantage of the library capabilities, and developers are advised to read the full tutorial and API documentation in order to make the most out of the library.

It’s worth noting that under the hood, Sheperd uses Floating UI, formally called Popper.js, a tooltip and popover positioning engine that ensures the dialog windows always remain visible and properly positioned.

While developers can use Shepherd out of the box with any framework, there are many user-maintained libraries to ease the integration (such as React Shepherd). Developers can find links to popular integration in the Shepherd Github repository.

Shepherd source code can be found at the official repository on Github and is provided under the MIT license.

Developers are encouraged to participate in developing and maintaining Shepherd by following the contributing guide.

About the Author

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

Why tech companies have venture capital funds | InfoWorld

MMS Founder

Posted on mongodb google news. Visit mongodb google news

February saw the announcement of yet another corporate venture fund, prompting CNBC reporter Jordan Novet to quip, “If your company has no corporate-venture arm, what is it even doing?” Novet’s comment came on the heels of MongoDB’s new fund (disclosure: I work for MongoDB), but the intentional irony strikes home because it comes on the heels of recent announcements from Databricks (December 2021) and Snowflake (November 2020), joining larger tech companies that launched their own venture funds years ago, including Salesforce (2017), Microsoft (2016), Google (2009), Red Hat (2000), and Intel (1991).

Why? What’s the point of these different tech venture funds? Are they merely a sign of well-funded partnerships?

Partnerships masquerading as investments

Sometimes that is surely the case. Though Salesforce launched its first $50 million Impact Fund with high-minded verbiage about benefiting society and social good, it also highlighted the goal to “strategically invest in companies built on the Salesforce Platform, delivering unique capabilities to Salesforce customers.” Could this be done through partnership? Of course. But investing arguably makes “some partners more equal than others,” to paraphrase George Orwell’s Animal Farm. Nor did it hurt that sometimes these investments have paid rich financial returns for Salesforce, netting it $2.17 billion in 2020.

In other words, there are likely all sorts of motivations in play for each of the corporate venture firms.

Take Red Hat, for example. The company was famously parsimonious under former CEO Matthew Szulik. (I once flew to Raleigh for a job interview with Szulik, and his first question was how much my flight cost.) Red Hat’s venture fund might have seemed an extravagant way to spend the company’s (then) small profits. Speaking at the time, Szulik stressed that Red Hat Ventures was intended to be “much more than a source of financing” and instead saw a need for “true partnerships” whereby “we accelerate their ability to reach the global Linux market and they enhance our ability to offer the broadest range of Internet solutions to enterprise customers.”

Think of these partnerships as a way to buy some loyalty from partners the investor needs to round out its product suite, even as the investor hedges its bet by accelerating the startups’ access to large markets. In Databricks’ fund announcement, it was quite clear on this: The “Lakehouse Fund will focus on early- and growth-stage companies extending the lakehouse ecosystem or using the lakehouse architecture to create the next generation of data and AI-powered companies.”

Creating markets

Put this way, a few hundred million here and there is a small price to pay for influencing markets to lean your way. Or, as MongoDB’s Serge Tanjga put it, “We are not just building a product; we are building an ecosystem.”

In a recent Grant Thornton survey of 150 tech CFOs, respondents were asked how their companies planned to fund growth during the next two years. Acquisitions notched the top spot (58%), followed by divestitures (25%) and nontraditional mergers and acquisitions such as special-purpose acquisition companies, alliances, and joint ventures (15%). When asked how they expected to reach new customers, direct selling (58%) came in first, followed by customer acquisition through third parties (25%). Corporate venture funding, in other words, isn’t the preferred way that tech companies seek growth. As one very unscientific source (Hacker News) suggests, marketing is arguably the top thing companies can and should do to find new customers.

Yet, it’s telling that companies as varied as Databricks, Salesforce, and Intel continue to pour copious quantities of cash into supercharged partnerships-qua-venture investments to attempt to move markets in their favor. Yes, companies will still do marketing, just as they’ll open source software or provide open APIs to increase developer interest, and/or build out partner programs to align corporate interests. Venture funds are just one more way that companies hope to “build an ecosystem, not merely a product,” to paraphrase Tanjga.

Do venture funds work? Those that have done them longest, such as Intel, seem to believe so. Intel Capital has invested billions of dollars in hundreds, maybe thousands of companies since 1991 and can point to both significant venture returns and support for Intel processors among its investment portfolio.

Money may be the ultimate takeaway. Intel, like Salesforce and other successful corporate venture initiatives, insists on financial returns, not just ecosystem development, as central to its investment thesis. Market-making is a difficult, long-term endeavor, and venture investment is just one contributing factor. The companies that do it best don’t seem to privilege strategic considerations over financial returns. If your company is considering a venture arm, perhaps you should take this approach, too.

Article originally posted on mongodb google news. Visit mongodb google news

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

Kotlin 1.6.20 Preview Features Context Receivers and Performance Improvements

MMS Founder
MMS Johan Janssen

Article originally posted on InfoQ. Visit InfoQ

JetBrains has released Kotlin 1.6.20-M1, a preview version of the upcoming GA release that introduces context receivers, several performance improvement options to reduce compilation time and a concurrent garbage collector.

IntelliJ IDEA or Android Studio should be configured to use the Early Access Preview features via Tools – Kotlin – Configure Kotlin Plugin Updates and then install the latest preview version. The application’s build scripts should be updated to the latest Kotlin preview version: 1.6.20-M1.

Context receivers provide support for multiple receivers, instead of just one, that may be added to the declaration of functions, properties and classes to make them context-dependent. All context receivers should be declared as implicit receivers in the caller’s scope. For example, by declaring an interface that contains a reference to Logger and then using the logger property in a function by declaring the LoggingContext interface as an implicit receiver:

interface LoggingContext {
    val logger: Logger 

fun saveUser(student: Student) {
    // Logic to save the user to the database"User has been saved in the database")

Currently, the -Xcontext-receivers compiler option may be used to create pre-release binaries in order to test the functionality. Since the feature isn’t complete yet, the binaries shouldn’t be used in production and there’s minimal support from the IDE.

The experimental JVM IR backend mode was introduced in order to compile all files in a module in parallel to decrease compilation time. The compiler option -Xbackend-threads enables this mode and the number of threads may be configured as either 0, which uses one thread for each CPU core in the machine, or a value smaller than the number of CPU cores in the machine. The tradeoff for decreased compilation time is an increase in heap memory which is proportional to the number of threads being used.

When the build is already parallelized by the build tool, then adding another layer of parallelization might even increase the build time. The JVM IR backend mode doesn’t work with the no-longer-maintained kapt annotation processors as kapt disables the backend mode.

Incremental compilation for development binaries with the Kotlin/JS IR compiler is now available after configuring

After enabling the incremental compilation, the compiler caches previous module compilations when using the compileDevelopmentExecutableKotlinJs Gradle task. Especially with smaller changes, the module caches can be used instead of compiling the modules again.

By default, Kotlin 1.6.20 enables hierarchical structure support for multiplatform projects to share source code across native targets to simplify the build setup and improve IDE support.

Performance of Kotlin/Native compilation has been improved by reducing execution time, binary size and compilation time by statically initializing some synthetic objects generated by the compiler and optimizing the compiler caches. The new memory manager reduces execution time and now contains a concurrent implementation for the garbage collection sweep phase which may be enabled with -Xgc=cms.

Support is available by registering in the Slack eap channel and issues may be reported in YouTrack.

About the Author

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

Java News Roundup: Spring Projects Updates, Value Objects (Preview) JEP, Quarkus 2.7.2

MMS Founder
MMS Michael Redlich

Article originally posted on InfoQ. Visit InfoQ

This week’s Java roundup for February 21st, 2022, features news from OpenJDK, JDK 18, JDK 19, Quarkus 2.7.2.Final, JReleaser early-access, and multiple Spring project updates: Spring Boot 2.7.0-M1, 2.6.4, 2.5.10; a new ListCrudRepository interface for Spring Data 3.0-M2; Spring Security 5.7.0-M2, 5.6.2, 5.5.5; Spring Session 2021.1.2, 2021.0.5; Spring Shell 2.1.0-M3; and Spring Batch 4.3.5.


JEP Draft 8277163, Value Objects (Preview), was promoted from Draft to Submitted status this past week, stating that the JEP owner, Dan Smith, has declared this draft as ready for evaluation towards Candidate status. This JEP proposes the creation of value objects, identity-free value classes that specify the behavior of their instances. This draft is related to JEP 401, Primitive Classes (Preview), and will provide continued contribution towards fulfilling Project Valhalla.

JDK 18

Build 37 of the JDK 18 early access builds was made available this past week, but there were no comparable updates from Build 36. With less than a month before the GA release of JDK 18, the updated release notes include links to documents such as the complete API specification and an annotated API specification comparing the differences between JDK 17 (Build 35) and JDK 18 (Build 37).

JDK 19

Build 11 of the JDK 19 early-access builds was also made available this past week, featuring updates from Build 10 that include fixes to various issues. More details may be found in the release notes.

For JDK 18 and JDK 19, developers are encouraged to report bugs via the Java Bug Database.

Spring Framework

It was a very busy week over at Spring as the team provided numerous point and milestone releases for Spring Boot, Spring Data, Spring Security, Spring Session, Spring Shell, and Spring Batch.

On the road to Spring Boot 2.7.0, the second milestone release was made available to include 137 bug fixes, documentation improvements and dependency upgrades. New features include: test annotations for Couchbase and Elasticsearch; enhancements to auto-configuration registration and ordering with the new @AutoConfiguration annotation; and support for OkHttp 4.9.3. Further details may be found in the release notes.

Spring Boot 2.6.4 has been released featuring 61 bug fixes, documentation improvements and dependency upgrades. More details may be found in the changelog.

Spring Boot 2.5.10 has been released featuring 52 bug fixes, documentation improvements and dependency upgrades. Further details may be found in the changelog.

The Spring Data team has introduced a ListCrudRepository interface for Spring Data 3.0-M2 designed to return a result set of type List instead of an Interable, the type returned by the well-known CrudRepository interface. The motivation is to offer developers a choice with a preferred return type when working with Spring Data.

On the road to Spring Security 5.7.0, the second milestone has been released that will deprecate the WebSecurityConfigurerAdapter class as a move towards a component-based security configuration. Developers are encouraged to read this blog post on using Spring Security without WebSecurityConfigurerAdapter and more details may also be found in the release notes.

Spring Security 5.6.2 and 5.5.5 have been released with bug fixes, minor improvements and dependency upgrades. Both versions introduce the AuthorizationManagerWebInvocationPrivilegeEvaluator class that serves as an implementation of the WebInvocationPrivilegeEvaluator interface which delegates the checks to an instance of AuthorizationManager.

Spring Session versions 2021.1.2 and 2021.0.5 were released this past week featuring dependency upgrades of versions 2.6.2 and 2.5.5, respectively, of Spring Session Core, Spring Session Data Redis, Spring Session JDBC and Spring Session Hazelcast and Spring Session MongoDB (for Spring Session 2021.1.2 only).

On the road to Spring Shell 2.1.0, the third milestone release was made available to feature initial work on a higher level UI Component model to enhance building more attractive interactions with users. An example may be found in the release notes.

Spring Batch 4.3.5 was released featuring bug fixes and dependency upgrades. Enhancements include: simplify the GET_LAST_STEP_EXECUTION field in the JdbcStepExecutionDao class to use an equi-join instead of an cartesian join with a subselect; add the @Nullable annotation the getEndtime() method defined in the StepExecution class; and implement argument checks of the setSort() class defined in the MongoItemReader class. Further details may be found in the changelog.


Quarkus 2.7.2.Final, the second maintenance release, was made available featuring dependency upgrades of Kogito 1.17.0.Final and OptaPlanner 8.17.0.Final. More details may be found in the changelog.


On the road to version 1.0.0, an updated early-access release of JReleaser was made available this past week featuring adding Windows resources to the configuration of jpackage, a tool that may be used to assemble distributions of type NATIVE_PACKAGE.

About the Author

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.

Podcast: Leading Beyond Change – Leadership for New Ways of Working

MMS Founder
MMS Audree Tara Sahota Michael K Sahota

Article originally posted on InfoQ. Visit InfoQ

Subscribe on:


Shane Hastie: Good day folks, this is Shane Hastie for the InfoQ Engineering Culture podcast. I have the privilege today to sit down across the miles with Michael and Audrey Sahota. Michael and Audrey, welcome. So great to see you again.

Audrey Sahaota: Thank you so much. Good to see you too.

Michael Sahota: Yeah, it’s really good. We’ve haven’t seen you in years.

Shane Hastie: It’s felt like a lot longer, but if I look back, it was two years ago almost when we recorded our last podcast, which was at Agile on the Beach. So before we get into that though, there’s probably some of the audience who haven’t come across you before. So would you mind just giving us the quick one minute introduction?

Introductions 01:12

Michael Sahota: So my background is actually I went through engineering. The brilliant guy who goes into really hardcore technology science. I did a master degree in computer science, have a PhD. I published papers in artificial intelligence, robotics. I switched gears and started working as a software developer, moved to architect roles, leadership roles, vice president of R&D, director of software development. And all very along, pretty much my whole professional career, I’ve been involved with Agile. Originally starting with extreme programming in 2000. I was really attracted to this because it’s like, hey, how can we do things better? That’s kind of like my constant drive.

How can we do things better? And when I switched gears working as a trainer and a consultant, helping organizations on the outside with Agile, with Lean, with digital, I realized something, is that Agile alone is insufficient. And I realized something else is that I wasn’t showing up in a way where I could actually really help leaders evolve, create environments where Agile could actually work. Where we could actually get the benefits we hope for. And so I went on this incredible journey of my own self-evolution and along the way, I just was trying to figure out, how do I be successful? How do I evolve myself? And how do I learn new patterns for interacting with people in organizational systems? And so years kind of culminated in this book. It’s kind of this level one sort of understanding of a very different way of looking at reality, looking at people, looking at culture, looking at what does it pay to create high performance?

And it wasn’t surprising for us emergent result was that Audrey and I co-create something in which we’re calling the SHIFT314 Evolutionary Leadership Framework or the SELF framework. It’s about scaling excellence with people and it’s really this rethink of pretty much everything. And people have part of the rethink and hear little bits and pieces here, but is that, how do we have a coherent way of looking at what’s happening now and choose a different path? So that’s kind of what my journey’s been like.

Shane Hastie: Audrey?

Audrey Sahaota: Well, I don’t come from an Agile background at all. Not really good with technology, although I am getting better and I am a Scrum master because when I was introduced to Agile, in order to work with Michael and to help develop the culture and leadership training, I really needed to understand where everybody was coming from and what they were doing. And along the way, I fell in love with Agile and I’m starting from the end and I’ll go to the beginning, but I really have a passion for shifting the way humanity functions on this planet and interrelates with each other.

New ways of way of working that require us to show up in a different way 03:35

Audrey Sahaota: And I found that Agile it’s actually embedded in every single organization on this planet practically. And it’s this new way of working that requires us to show up in a very different way. So I come from an energy medicine background, which actually means that I do energy work, some people call it spiritual healing. I don’t really call it that, but I work with energy to help people heal. And the foundation of that is studying the psychology of disease, thoughts, belief systems, and conditioning in our life experiences actually create disease in the body. And our physical forms eventually will start breaking down as low vibrational energy hits our physical form we start to break down and why is this?

Is because the way we’re relating to each other, the way we’re relating to ourselves, the way we’re showing up in our lives, our environments, both psychologically and physically are just very, very toxic. And so I had this crazy idea, I was working on a medical team in Chicago for five years and I was working with very ill people. And I really just wanted to find a way to make a bigger impact with humanity. And I thought, gosh, if we can go into an organization and shift the mindset, the consciousness of the leaders who actually are the ones that have most influence on how these organizations are functioning, the workforce that is working in these organizations and the products and the services that they’re creating, this will ripple out into the world. So if we can start with the leaders and work our way down, that would be the fastest way I see it to shift humanity.

So when I’m met Michael, I actually met Michael in India and I told him this crazy idea before I knew who he was or what he did. And he was just like, “Oh, that sounds interesting.” You know? And then when he invited me to come to one of his certified Agile leadership courses to actually coach him because of what I wanted to do, I started to train as a professional coach. And so I came to coach him and seeing the flip charts on the walls and the post-it notes and all these people talking about these new ways of working and people-centric, I was like, oh, my God, there’s hope for the planet. And this is exactly what I was talking about. And that was almost five years ago now.

Michael Sahota: It’s almost five years ago.

Audrey Sahaota: And we’ve written two books and we’ve created amazing courses. And I get to wake up in the morning, really excited about life.

Shane Hastie: And you’ve become a couple?

Audrey Sahaota: Yes, we have.

Michael Sahota: But there a right sequence, step one, fall in love. Step two, figure out how to be together in the same place in the planet.

Audrey Sahaota: I like the before and after pictures because it’s really a testament to my amazing coaching, I think is Michael Sahota before Michael Sahota after and I just show that to my clients. And they’re like, oh, my gosh, I’ll take full credit for Michael Sahota.

Shane Hastie: Let’s explore a little bit, the latest book, Leading Beyond Change. What’s the intent there?

Leadership, high performance and how we approach change are all one topic 06:46

Michael Sahota: The title says it all. It’s about understanding leadership, really high-performance culture, how we approach change. These are all one topic that we’re looking at from different dimensions. And when we see them from an elevated, more conscious, more aware perspective, it actually unlocks all dimensions. So you can think of the title in different ways. It’s about how do we lead into the beyond on our team, in our department, in our organization. And how do we move beyond what we usually think about change?

The current patterns from change that we see happening in organizations, even in the name of Agile are barbaric, horrific, demotivating, disengaging, and actually work against what people are saying the goal is. So it’s about really understanding what is the beyond? What is the future of work? What is the potential of human beings to work together to create high performance and amazing products? And really 80, 90% organizations are traditional business patterns which are trapped in like a historical legacy of command and control behavior that most leaders are conditioned into and not even aware that they’re operating that way.

Audrey Sahaota: In a nutshell.

Shane Hastie: So what do we do about it?

Changing the paradigm starts with awareness 07:52

Michael Sahota: Step one, before you can change anything you have to become aware of the problem. So one level of the bulk is like a big awareness. It’s just a big awareness of like, wow, we are trapped in traditional business as usual patterns and it’s creating extraordinarily bad results and I’m responsible for it. And how do we do that? We give people a series of patterns, patterns of this is what a traditional organization looks like. This is what an evolutionary one looks like, and these are the consequences. So we’re helping people understand like the laws of cause and effect like, well, when you treat people better, they perform better. If people aren’t performing the way you want them to, why don’t we just examine how you’re treating them? It’s dumbing down the whole book to like a really basic idea.

You use the term evolutionary organization. What does that mean?

What is an evolutionary organization? 08:40

Michael Sahota: Okay. So everybody wants the ability to be adaptable, to thrive in a VUCA world. From Agile, we talk about respond to change over following a plan in order to respond to change it means we have to have a characteristic called adaptability. Adaptability at a personal level and an organization level. So evolutionary captures the notion of what kind of people, cultures, organizational systems have that evolutionary capability? They’re able to evolve in the face of the changing needs and demands of what’s happening externally and internally within a company. That’s what we mean by an evolution organization. Now it’s roughly synonymous, you want to think about like a Teal organization. Most Teal organizations have that evolutionary capability, exponential organizations, people are talking about really high performance organizational systems have this kind of characteristic. But what we’ve done is there are many, many ways to talk about something but when we talk about it is what is the evolutionary capability of the system?

The evolutionary capability of the system is dependent the evolution and capability of the people because the people make up the system 09:32

Michael Sahota: We go, wait a second. Well, the evolutionary capability of the system is dependent the evolution and capability of the people because the people make up the system. Then we go back as well, what is my rate of evolution as a human? What is my rate of evolution as a leader? Then it ties directly into the concept of evolutionary leadership, which is a choice as a human being to evolve myself, to learn the tools and capabilities needed to evolve an organizational system. And so it’s really kind of waking up to say, well, look, there’s an important dimension we’re not even aware of, which is what is my rate of evolution and what are my evolutionary capabilities and how do I acquire more? But first understanding, where am I?

And so when we understand that we understand that it’s a journey for each of us to develop more evolutionary capabilities, to increase our evolutionary capabilities so we can help others increase their evolutionary capabilities so organizational systems can be more adaptable, really deal with all the changes and when everyone’s learning, and we’re just going beyond the learning mindset to what we call an evolutionary mindset, ready to learn about ourselves. When everyone’s learning at such a great rate, that’s what gives us the adaptability, right? So we’re actually getting people to focus on what’s most important to lead to the outcome that we want.

Shane Hastie: The cynic in me says, but this is all fluffy. How do I put this in practice? And I think of the target audience for InfoQ, the people who are listening to this, many of them are mid-tier or new leaders in technology teams. How do I bring this into the work that I’m doing on a day by day basis as a team lead or maybe a little bit higher, but in that technology area?

Culture bubbles – create a bubble of more evolved culture around your team 11:05

Michael Sahota: That’s a great question. And everything we’re talking about here is open to every leader at every level because there’s a technology and there’s a pattern in the book that goes into the details that’s called Culture Bubbles, where each person can create a bubble of a more evolved culture system that has higher performance characteristics. It’s not about waiting for some leader above you to change. No. It’s about how to empower every single person. Now I’m going to go back before we get into the practical pieces, why do we need this shift? We’re so conditioned to this masters of business administration, of business as usual paradigm. We actually need to learn how to lead. So this is what this technology does is how do you actually lead to help your people become engaged and motivated.

The role of the manager is to focus on increasing the production capability in their team 11:41

Now just very practically let’s just talk about one characteristic. You know, we have a learning culture here and what you can do is you can look at your team, let’s be very practical. What percentage of your time is your team focused on production? Getting projects done, delivering things and what time is focused on production capability? And we get sucked in the trap in a traditional world as a manager to focus on production. Whereas our actual job is to focus on increasing the production capability, the system too so-called look after our people. And when we understand that, oh, that’s what’s the most important thing I need to do. I need to not just manage production but production capabilities so that month by month, quarter by quarter, year by year, our system is more productive. And how do I, as a leader, bring that about?

Michael Sahota: The first one is a shift of thinking and it’s like, okay, well it’s determined by my rate of evolution of how good I am at helping unlock my people. Oh, so I need to evolve myself so I can help my people evolve so we can get a higher level of production capability to get even better results here. You know, whether it’s more customer-centric outcomes or greater throughput or whatever the performance constraint or goal in the system is, how do I better meet my objectives and really do such an awesome job? I get promoted, get a bigger salary, blah, blah, blah, blah. Right? But that’s really the focus is understanding, what do I need to do to win not just this quarter, but to set up for the next quarter?

You know, Alistair Cockburn talks about in his original book on Agile, going back to 2001, there’s two competing games. There’s the immediate game and then there’s this, he calls it Product Development Game. But the product as a manager is actually your team. You ship your team. So how do I as a leader, how do I as a manager elevate my team so that we ship amazingness. Oh, I don’t know how to do that very well. Oh, okay I better learn how to do that if I want to be successful in my role. So it’s something very practical, something very tangible. And the book gives people, the maps to orient because is what the self framework is.

The maps to orient and understand what’s the journey. How do I understand what I need to do? Where to focus? The principles to guide behavior. The models to reason about and understand what’s happening around us so we can actually take good actions, run good experiments and very practical tools. Very, very practical tools to say, what do I do day in day out to break out of this traditional into a set of behaviors that will allow me to unlock the people around me and unlock performance. That’s why it’s called a Practical Guide to Business Agility or High Performance.

Audrey Sahaota: Right. Because without action none of it makes any sense or is even worth talking about. So I’m a stickler for, okay, everything that we develop, how do we put it into action? How do we give people something that they can take away tomorrow? And sometimes the concepts are a little bit simple like listening or creating equal voice or psychological safety or how you’re going to show up to create an amazing team meeting, mapping out your organization with heat maps to see who’s ready and who’s not ready. So when you’re going through a transformation, you’re not pushing into the system creating resistance because it turns out that people are terrified when there’s a transformation going on, they don’t know, are they going to have a job? What is their new role? What is this crazy new way of working? Or even if they’ve been doing Agile for a while, but the other part of the organization is not doing Agile how are we going to interact with other parts of the organization to be inclusive?

And it’s funny because I think in our hearts, we want to be inclusive. We want to be collaborative. We want to work together and we want to create amazing organizations. But when there’s a crisis, how are we showing up? We’re talking about culture and we’re talking about high performance and it’s the little tiny things that make these huge difference in high performance. Because when we’re in fear or we’re stressed out or we’re under a lot of crisis that’s going on, how are we showing up as leaders, as team members is going to either lock up the system or it’s going to unlock the system. So there’s the mindset or the consciousness or the way of being, and there’s also doing. Are we going to continue our habit of command and control behavior or are we going to start utilizing the tools that we have available to us with all these new Agile ways of working? Are we actually going to stick to it and use them no matter what’s going on?

Shane Hastie: So some solid stuff in there let’s get more concrete. How do I change if I recognize, yeah, I have these command and control habits because I’ve learned this. This has often made me successful by whatever measure we want to use for success. And I acknowledge that there possibly is a new way. How do I lean into that new way? How do I start the change journey?

Actionable advice for leaders 16:34

Michael Sahota: Success follows desire. So what the book does is really to help people understand the damage they’re causing, right? And when we start to understand the damage we’re causing what’ll happen is we realize the way we’re functioning as a leader is wholly unacceptable in terms of creating a high performance result. Once we have that awareness, then we can open to stage two, which is, oh, there’s some new behaviors. There’s some work I can put into this to change how I show up. Got it. Okay. You know what? That’s scary. I don’t know if I want to do that. I don’t know if I’m ready to evolve. I don’t know if I want to change. That’s where we talk about evolutionary leadership being the choice to evolve until leader definitely makes that your choice to step into the unknown. But think about it, what’s Agile about? It’s about being comfortable with uncertainty.

How can you be a “Agile leader” unless you’re ready to step in the unknown yourself? No, no. I’m just going to tell other people to step in the unknown. We’re just going to tell the product owner they’re not going to get a date and it’s unknown and uncertain they can deal with it, but I don’t need to deal with it. So we’re just talking about basically eating your own dog food. If you’re really talking about an Agile environment, we’re just saying like, did you notice you’re not living at a personal level? Like you are not living the Agile mindset basically. I mean, that’s what we’re saying here. People are saying that we’re Agile and we do retrospect literally day in, day out, meeting after meeting. People are not putting people first. They’re not modeling a learning culture. They’re not in their personal ability, adapting to change. When something change happens, unexpected change, they react really badly like, whoa,

Audrey Sahaota: It’s not their fault.

Michael Sahota: It’s not your fault if you’re thinking, shoo, I’m doing that. That’s what my realization was. I wasn’t living the Agile mindset. After working with Agile for over a decade, I was not living the Agile mindset. I was an expert in the practices. I could go head to toe with anyone in the world, but exactly how Agile works, but I wasn’t living the mindset. I wasn’t actually living the behaviors. I wasn’t putting people first in everything I did. I wasn’t focusing every move I could make to help other people show up as brilliant leaders.

Shifting consciousness as a leader 18:34

Audrey Sahaota: So you asked a really interesting question about how do you change your behaviors. And what people don’t really understand is because we come from a Western context is that we come from a deep understanding or may maybe a general understanding of psychology and psychology while good and while beneficial has an industry developed on long term, long term talk therapy, there’s even other therapies that are out there that are a little bit more progressive. We have taken what we’ve learned in the Eastern traditions, which has a technology to shift consciousness very quickly and we’ve integrated it into our curriculum. And so we’ve developed our own specific exercises and techniques and tools to help shift your consciousness very rapidly. And when I say consciousness, I’m talking about your mindset, your worldview, your perceptions, your behaviors, and your conditioning, but it is taken from these Eastern philosophies and practices that we learned and we experienced.

And I know for myself, I can speak probably for Michael as well, is that some of these techniques, as simple as they are, are really, really difficult to do when you’re looking at contemplating how you’re showing up as a leader and the damage that you’re causing and the impact and the consequences, that’s really hard. Leadership is about being responsible and having the power and the responsibility. What we don’t really do a lot of times is we don’t really become brave enough or have the courage to step inside and really take some inventory about our impact on the environment and our relationships. And once you can do that, that alone is enough to start to shift and rewire your brain and your habits. And so that’s why it sounds really simple. It’s more difficult to do.

Shane Hastie: I want to go deep. I want to explore that.

Audrey Sahaota: Okay.

Shane Hastie: What do I need to do? So now I’m sitting as this leader, I’m perhaps getting to a point of consciousness that, hmm what I’m doing isn’t right. Isn’t working well, it may have served me well in the past and I can see the impact now. And you’ve opened my eyes to, there are different ways of achieving the outcomes that we want. And we all want to be good people. We all want the best for our organizations and for the teams that we are leading, but maybe I haven’t done this terribly well.

Michael Sahota: So it’s okay. So the truth is that we’re all on our journey. We all have adaptations to our nervous system that causes great destruction around us. We’re all in various ages of letting go of the command and control habit due to our parents conditioning us and telling us what to do when we were young children and so on. So we’ve had this basically drilled into us since birth. So we’re talking about a deep reconditioning program here, but here’s the good news awareness is the technology of shifting consciousness.

Audrey Sahaota: 87.6% of the journey.

Michael Sahota: So what happens is very simple. When you choose to start, well, let me be aware of the damage I’m causing. Let me take these patterns from the book and really become aware of when am I falling into these traps? 90% of the work is just stopping the damage. It’s not about necessarily learning new behaviors. Those will happen naturally over time. It’s a learning journey no problem. People are good intention and we see it all the time with people trying to move to Teal or Agile, let’s jump to the solution. And we’re saying, please, don’t do that. Please just stop. Because the only place you can start is where you are. Start with the truth of where you are and stop causing the damage of what you’re doing now, which requires not having this, you know, oh, we want to have transparency in our organization.

And we want to self empower all the teams. It’s like, no people aren’t ready for that. Like start where they are. They’re in mixed levels of engagement and you’re going to get mixed levels result if you try to share all the power so rapidly and let’s just do this in a gradual journey. It’s kind of like basically applying Kanban to organizational evolution. It’s just a very… To really dumb down the whole thing at both a personal level and an organizational level. Kanban says, look at what’s happening in around you. Same thing. Just look at what you’re doing as a leader and make gradual change. It’s a really simple choice when you have the awareness and you know what you’re doing wrong.

Audrey Sahaota: What I would say, if you were my client, I would actually have you understand or feel into what is going on in your inner world that’s creating the push or the mandate or the passionate desire to make my teams go Agile. Like you can feel it. Like I can feel it inside of me like all of a sudden there’s a tightness in my inner being. And all of a sudden I’m feeling a little stressed out because now I have to perform and I have to make all these other people perform. And so one of the more practical things on just a personal evolution level is to really start to identify and become aware of this underlying drive that’s a fear-based anxiety ridden survival mode way of being. And that’s actually underlying everything that you do. Every interaction that you have, every email that you send, every time you, well now we’re not walking into the office so much any more, but even on the Zoom calls and we’re feeling beings, we can feel each other and you’re transmitting like anxiety, fear, terror and survival mode.

And so if you can just dial it back to an awareness of that, and we talk about it in our other book, Emotional Science, but real really becoming aware of, oh, that’s my inner state. And that inner state, that is where I’m functioning from 24/7 in my relationships at work and at home. And so that’s kind of where you start with yourself, you know?

Shane Hastie: Yeah. So much of what I’ve learned about leadership and changing leadership behaviors and leading organizations is it starts with this self-awareness and that’s really hard for many, many people.

Self-awareness is the crucial starting point 24:55

Michael Sahota: That’s why we created a workbook to go with Leading Beyond Change. We put a lot of effort into it and the workbook is a free download from website. And what it does is every time you go through a chapter or a pattern, it asks you to reflect on the questions. And so most people will just skip over this. They go, “Oh, I’m just going to read the book I’ll get the information and knowledge.” No, no, no, no, no. The whole book together with the workbook is designed to shift your consciousness because awareness is the technology shifting conscience.

Michael Sahota: When you take the time to journal and do the exercises, it will actually create a shift. You’re a trainer, you know this, when people actually do something with the information it gets integrated, right? So they get integrated this understanding like, oh, whoa, this is bad. Ooh. And then when you’re doing in the office and you’re going, whoa, something’s wrong here? Oh, this is bad. What am I doing? Right. Boom. You wake up. And suddenly you snapped out of having a moment of causing damage, disengaging your people, oppressing them, acting like a command or control boss and you can make a different choice.

Shane Hastie: I think that’s a good point for us to wrap up on. If people want to explore this further, where do they find the book? Where do they find you?

Michael Sahota: The best place to find us is our website and there’s a link to the book there. It’s also an Amazon, Leading Beyond Change.

Audrey Sahaota: Well, there’s also-

Michael Sahota: There’s also an audiobook.

Audrey Sahaota: There’s sampled chapters-

Michael Sahota: Download for free. Yeah.

Audrey Sahaota: There are all kinds of stuff. We really just want to help people be successful. A lot of times we’re just offering as much valuable information as possible because it’s tough out there and we don’t have a lot of places to go. And I think when we have the tools and the techniques to do the job, we’re more willing to show up to do the transformation that we’re all here to do together.

Shane Hastie: Michael, Audrey, thank you so much for taking the time to talk to us today.

Audrey Sahaota: Thank you for having us here, Shane.

Michael Sahota: It was our pleasure. Great seeing you.


About the Authors

QCon brings together the world’s most innovative senior software engineers across multiple domains to share their real-world implementation of emerging trends and practices.
Find practical inspiration (not product pitches) from software leaders deep in the trenches creating software, scaling architectures and fine-tuning their technical leadership
to help you make the right decisions. Save your spot now!

From this page you also have access to our recorded show notes. They all have clickable links that will take you directly to that part of the audio.

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.