Speed: Processing on the device instead of sending to the cloud and waiting for an answer is way faster (latency)
Offline-capability: Edge devices can operate independent from a network / cloud connection
Real-time communication on the edge: Edge devices can communicate between each other directly, which can be done much faster due to the short distances and also more efficient as the power and information of several devices can be combined (for more info see: ultra low latency networks, peer-2-peer, M2M actions)
Vivien: What is EdgeX and where are you at with it?
Michael: EdgeX Foundry is a vendor neutral open source platform containing a collection of micro services that take care of different aspects of what you’re going to need to have an edge computing platform. If you’re making IoT devices, you don’t want to reinvent that layer of the stack. Having that common platform for IoT is something that is going to benefit everybody. The Linux Foundation is a neutral umbrella over EdgeX. Inside the project are all the member companies who are actually funding the development, putting developers and marketing resources in, to make it an actual, usable product for everybody. That’s the model of the project and the actual code itself. The main goal of EdgeX is processing and transporting data between IoT devices and sensors and things in the cloud and on the backend. The focus is on being able to respond locally as much as you can, so that you don’t have the latency of going on the cloud and back. And also, being able to continue working, if you loose that connection.
Jim: EdgeX is a an open source platform containing a collection of micro services that take care of different aspects of what you’re gonna have to do to have an edge computing platform. Any of those are semi-dependent: You can replace anything you need to replace. For the status of the project: We just had a year of fast pace growth and we have rewritten everything in Go, so all of our processes are a lot smaller and more efficient now.
Vivien: How are you currently tackling local on-device data persistence?
Jim: We currently use Mongo DB as the persistence engine although we could support almost any kind of persistence store at the edge as long as it was small enough. We also have used SQLite in the past for a couple of customers. However, Mongo DB is the largest element in our portfolio of services. There are a couple of reasons why we are probably going to offer an alternative to Mongo with our next big release in spring 2019: Footprint, licensing, and lack of support for ARM32.
Michael: As we are a collection of microservices, you can always swap out individual pieces depending on what your needs are.
Vivien: Is EdgeX and its components restricted to certain licenses?
EdgeX builds on Apache 2
Jim: EdgeX is an Apache 2 license open source project, so we prefer Apache 2 level or at least a compatible license, because we want to be very business friendly. We want people to take the application and use it in all sort of settings, including actually embeddeding it in gateways. We also want to be very decoupled at discrete points.
For example, if I’m a company like Dell and I use EdgeX. If some of my customers have an absolute demand that a certain database be at the heart, then I want to be able to choose the database, depending upon the customers, the use cases, and the environment that they find themselves in. EdgeX is all about the flexibility. So, for this example, we offer what we call a reference implementation database. Customers or users could take EdgeX and replace elements with their own technology, which may not be open source even.
Michael: You can take what’s open source and add proprietary file systems or hardware depending on what your specific needs are. EdgeX tries to be that common open source base. It provides all of the functionality in a open source license but that still lets you replace bits as needed with whatever it is that you want to run.
Vivien: Can you give us an example how and where EdgeX is currently used?
Jim: There are over 70 companies now that are part of the EdgeX community and each group is using it differently. There are some that are serving EdgeX as the Red Hat model: they are providing distribution, services and support behind EdgeX. A company like mine, Dell, we’re trying to find a platform that actually goes on our gateway. So we’re going to build a commercial version of EdgeX for our own platform. There will be pieces that we will replace based on better performing mechanism to some of our cloud based products. Then you have other groups out there that are proving particular services for EdgeX, for example edge analytics. There are lots of different service capabilities where we see potential replacements. Then there are companies like Samsung that uses EdgeX in their factory floor to help run their automation. So, they are users, but they also want to make sure EdgeX meets their needs. Our community is made of snowflakes, they are all very special *laughs* – common goals but different use cases for almost everybody that is part of the organization.
Vivien: That sounds really cool. In your opinion, moving the data to the edge, what is the edge, where do you see the data ending up, for example more on the sensor level or gateway level?
Latency concerns, cost of shipping up the data, and the ability to actuate locally are key reasons why you have to have edge software.
Vice Chair of the Technical Steering Committee, EdgeX
Jim: We absolutely believe EdgeX is a mechanism for the edge. While you could run pieces of EdgeX on the cloud, we do not believe is what the future holds. There are gonna be certain use cases where that works, but latency concerns, the cost of shipping up the data, and the ability to actuate locally are all key ingredients and reasons why you have to have edge software and edge platforms. Now, these are gonna get smaller. At Dell, we are manufacturing gateways of different sizes, because we know that certain use cases are gonna dictate a larger box and other are going to dictate something like a Raspberry Pi or even smaller. We have companies in our foundry that are looking at running parts of EdgeX in things like PLCs, to help address their realtime needs. So, we absolutely believe that the edge is very much going to be a part of our IoT environments. There are going to be use cases that dictate different levels of compute all the way up from sensors to cloud.
Michael: And all of our member companies see a need for that platform, but that platform is not going to be their product or their service. So everybody wants it to exist, so everybody is gonna work together to make it exist, so that they can build their own value-add on top of that or below their device level. Everyone agrees that this is an important thing, that we have to have a solution there for all the innovation that people see on the horizon.
Markus: So, small device level versus gateway – would you say your current focus is on the gateway?
Levels of Edge Computing
Jim: I would say that it really isn’t that one or the other is more important. You’re gonna have situations, as we know from a Dell perspective, where what we call a brownfield device (e.g. a 1979 modbus engine) needs a gateway, because it doesn’t have the ability to communicate into any kind network otherwise. So there has to be a gateway that provides that first level of compute. There are other things that are evolving in the industry: think of say windmill generators, where there is lots of capability right there at the device level, there is a lot of compute built right into those systems. So things will run at that level, and then you have everything in between. Even something like BLE or Zigbee type of environments where there is wifi and ability to connect directly to a network. Typically, we’re finding organizations are reluctant to allow those kind of things to connect into their major networks without some security, apparatus and analytics to see what’s going on, so as not to create problems in their larger networks. So even there, a gateway may be necessary, not because of hardwiring or physical connections, but because you want some insurances in place at the edge before that data leaks on up to your enterprise.
It’s the worst way to build our product except for all others.
Vice Chair of the Technical Steering Committee, EdgeX
Vivien: What’s the worse about open source that you’ve experienced?
Jim: *laughs* Now you are going to make me say some things in front of Brett and Michael as members of the Linux foundation… There is a quote by Winston Churchill that talks about democracy, saying it’s the worst form of government except all others. I kind of feel the same way about open source development. It’s the worst way to build our product except for all others. Because it does take time. It’s a community effort and anything done by a community automatically seeks a ground where it’s going to be the best and brightest product. So you get the best input from everybody, but it takes time. It’s easier for say something like Dell to go marching off and build a software solution that they think is the best. It will get there faster but it’s not necessarily going to get there in a way that the world and communities accept more easily. So anything built by many hands is going to take a little bit more time and a little bit more process. But it ends up getting a lot better results I think in the end.
Michael: Whenever you have a community building something you can’t just come in and say “This is what you’re gonna build” because they don’t have to do what you say. And that’s true even with EdgeX. Everybody who is working on it is working for a company invested in it, but there is no one person who can say this is what you’re all going to do. So it’s not enough to say just what you want done. You have to explain and justify why and get people to buy into that. And that takes more effort, but you have to know that what you’re proposing is the right solution, that it’s going to work. If you can’t explain that, you can’t communicate that to the community then it’s not going to get done. As Jim said, it takes time but at the end product is going to be better.
Jim: In this case with IoT, I will tell you that no one company will be able to provide it all. As Dell, we would love to be the company providing it all… (laughter) We have learnt the hard way that in an IoT landscape there are going to be certain things in the company that you can’t touch and IoT has to touch everything. Maybe it’s the network, hardware or operating systems, particular sensors and protocols. You can help to persuade customers to do some things in your way, but you’re never going to be able to get them to do everything in your way and that’s why IoT takes an ecosystem. Which is why we think the second part of EdgeX is so important; our product is important, but just as vital is the ecosystems. We have a collection of companies all trying to work together to provide for interoperability. That is just as important as the actual end product we develop.
No one company will be able to provide it all.
Vice Chair of the Technical Steering Committee, EdgeX
Vendor lock-in is not going to work in IoT.
Developer Advocate, Linux Foundation
Michael: Vendor lock-in is not going to work in IoT. There is no way any company is gonna be able to provide all the needs of somebody. So having an equal playing field for everybody, having that common ground that anybody can come to and interact with anybody else, is what’s going to allow us to fulfill the promise of IoT in general.
Startup Sesame is a one-of-a-kind program that connects European founders to European event organizers, bringing startups to amazing events throughout the year. While the exposure to events is great on its own, what’s even better is the network, on-site intros and especially the team behind it: Ben Costantin and his crew (@startupsesame).
Why Startup Sesame?
As a startup, you usually cannot afford to go to many conferences; however, a well-planned event can give you media exposure, great connections, sales leads, new ideas and generally provides you with learning opportunities along the value creation chain of your startup (from customer experience, networking, to closing a deal). It also gives you a great “reason for reaching out”. Yet, filtering out tons of events and which to attend, researching and planning the event in advance, and then performing on site and catching up with everything afterwards is a lot of work. Having a partner like Startup Sesame that helps you navigate that jungle, getting in touch with people on site, and last but not least with the financial costs, is invaluable. Even more, Startup Sesame not only sponsors most event tickets, they also provide additional opportunities to make use of the occasion like e.g. competing in the pitching competition, having a booth.
Then during the weekend, you get educated about the current startup ecosystem, the events, trends and most importantly the opportunity to pitch and get feedback on your pitch.
This weekend allows the Sesame team and the startup organizers to get to know you and your business. This way, they can learn how to best help you and make unique recommendations on events and competitions to apply to. It also gives you the opportunity to understand what VCs and event organizers are looking for in startup competitions and on-stage talks, which events make sense for you, and how to go about these opportunities to really make use of them for the business. It also helps you refine your pitch.
After the weekend, you receive additional feedback and mentoring and then, during the following year you are presented (actively!) with event opportunities that match your startup and personality. Also, they assign #rockstar #mentors to you that help you make the most out of your event attention on site.
Every year is organized differently. In our 2018 cohorte the setting was special: We were spending the time all together in shared rooms in a youth hostel at the Valencian beach. Food and coffee was a bit restricted, so we all needed to share and pay attention to each other’s needs. This brought the cohorte closer together than I think would usually have been the case (also great for the more introvert people… :D).
Who is Ben?
Ben is the founder and leader of Startup Sesame. Ben’s superpower is connecting people, or rather the right people; people who can benefit from being connected. Ben has a big heart, is very kind, and I believe he truly enjoys helping founders — and this really is what shapes the spirit of Startup Sesame. I am grateful to be part of the Startup Sesame Family (#proudsesamer).
Is it worthwhile?
For ObjectBox the answer is Yes. Once the next applications open I can only encourage you to apply. Just one word of warning: They give you tons of opportunities and in all likelihood, you can’t handle them all. E.g.: We needed to be very selective due to time constraints and it was/is hard to see many great opportunities pass by unused. However, you can check out what the #proudsesamer of 2018 have achieved in the last months on @startupsesame — it’s impressive and entertaining. 😊
These are the kind of events that you can attend as part of Startup Sesame. It was a great experience and lots of fun, but also added great value to our fundraising.
Or, if you are at dmexco 2018 or SaaStock 2018, you can join my talk on Open Source and Edge Computing. We can meet up there too 🙂
If you’re heart is in coding, you will love working with us. Then there are just a few additional things we are looking for:
“Equivalent to” 7 years+ professional software development experience
Professional C++ skills
Deep experience with network programming and OOP
Professional iOS and Swift project experience is a plus
Deep CoreData knowledge is a plus
Experience with Node.js is a plus
If you’re still reading, chances are you are the right person to join us in some way. Then, please send us an E-Mail (join[at]objectbox.io) and let’s have a chat. We’re very open for all kinds of collaboration.